Triple
T5553744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolidated Rail Corporation |
E145586
|
entity |
| Predicate | dateAcquired |
P2754
|
FINISHED |
| Object | 1999-06-01 |
—
|
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: 1999-06-01 | Statement: [Consolidated Rail Corporation, dateAcquired, 1999-06-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateAcquired Context triple: [Consolidated Rail Corporation, dateAcquired, 1999-06-01]
-
A.
acquisitionDate
chosen
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
B.
accessionDate
Indicates the date on which an item, record, or entity was formally added to a collection, system, or repository.
-
C.
dateAbsorbedApprox
Indicates that one entity was absorbed into another on an approximate or uncertain date, rather than on a precisely known date.
-
D.
acquisitionCompletedYear
Indicates the calendar year in which an acquisition transaction was fully completed.
-
E.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ff9c9c48190b5e587d58c6515d8 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.