Triple
T2395121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Pacific Railroad |
E47630
|
entity |
| Predicate | operatedUntilCentury |
P5251
|
FINISHED |
| Object | late 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: late 20th century | Statement: [Southern Pacific Railroad, operatedUntilCentury, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUntilCentury Context triple: [Southern Pacific Railroad, operatedUntilCentury, late 20th century]
-
A.
operatedUntil
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
B.
ceasedOperationsCentury
chosen
Indicates the century during which an entity stopped operating or ended its activities.
-
C.
developedSinceCentury
Indicates that something began to be developed or came into existence starting from a specified century onward.
-
D.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
E.
existedInCentury
Indicates that an entity existed or was present during a specified century.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc879b1b88190be8d0337d9a17bd0 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.