Triple
T29975746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In the American West |
E761440
|
entity |
| Predicate | endTimeOfProject |
P140
|
FINISHED |
| Object | 1984 |
—
|
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: 1984 | Statement: [In the American West, endTimeOfProject, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeOfProject Context triple: [In the American West, endTimeOfProject, 1984]
-
A.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
B.
workEndTime
Indicates the time at which a work-related activity, shift, or task is scheduled or actually finishes.
-
C.
endAt
Indicates that an event, process, or state concludes or terminates at a specified time, location, or condition.
-
D.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
eventEndTime
Indicates the specific time at which an event concludes or is considered finished.
- F. None of above.
Provenance (3 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 29, 2026, 6:33 p.m.