Triple
T2395118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Pacific Railroad |
E47630
|
entity |
| Predicate | acquisitionCompletedInYear |
P15703
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Southern Pacific Railroad, acquisitionCompletedInYear, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionCompletedInYear Context triple: [Southern Pacific Railroad, acquisitionCompletedInYear, 1996]
-
A.
acquisitionCompletedYear
chosen
Indicates the calendar year in which an acquisition transaction was fully completed.
-
B.
acquisitionAnnouncementYear
Indicates the calendar year in which an acquisition is publicly announced.
-
C.
acquisitionDate
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
D.
accessionYear
Indicates the calendar year in which an item, record, or entity was formally added to or registered within a collection, system, or institution.
-
E.
originalCompletionYear
Indicates the year in which something (such as a project, work, or construction) was first fully completed.
- 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.