Triple
T10650510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Stock Yards |
E250954
|
entity |
| Predicate | endTimeOfProminence |
P87454
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Union Stock Yards, endTimeOfProminence, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeOfProminence Context triple: [Union Stock Yards, endTimeOfProminence, mid-20th century]
-
A.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
B.
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.
-
C.
endTimePosition
chosen
Indicates the temporal position or point in time at which an event, state, or interval comes to an end.
-
D.
endTimeOfRole
Indicates the point in time at which a particular role or position held by an entity concludes.
-
E.
moreProminentSince
Indicates that one entity has become more prominent or noticeable relative to another entity starting from a specified point in time.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfe4b97081908815b77612222318 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.