Triple
T33463956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scaffold |
E856995
|
entity |
| Predicate | dateOfControversy |
P192664
|
FINISHED |
| Object | 2017 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2017 | Statement: [Scaffold, dateOfControversy, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfControversy Context triple: [Scaffold, dateOfControversy, 2017]
-
A.
dateOfConflict
Indicates the specific date or time period when a particular conflict, battle, or hostilities took place.
-
B.
contestedAt
Indicates that an event, claim, or outcome is being challenged or disputed at a particular time or place.
-
C.
dateOfSituationAddressed
Indicates the date on which the situation, issue, or circumstance being referred to is (or was) addressed or dealt with.
-
D.
debatedAt
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
-
E.
dataControversy
Indicates that there is dispute, concern, or disagreement surrounding the collection, use, interpretation, or ownership of certain data.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 1, 2026, 1:37 a.m.