Triple
T5553736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolidated Rail Corporation |
E145586
|
entity |
| Predicate | becameProfitable |
P65339
|
FINISHED |
| Object | early 1980s |
—
|
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: early 1980s | Statement: [Consolidated Rail Corporation, becameProfitable, early 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameProfitable Context triple: [Consolidated Rail Corporation, becameProfitable, early 1980s]
-
A.
profitsFrom
Indicates that one entity gains financial or material benefit as a result of another entity’s actions, existence, or situation.
-
B.
prosperedFrom
Indicates that one entity gained benefit, success, or advantage as a result of another entity, event, or circumstance.
-
C.
gainedBy
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, or event.
-
D.
gainedFrom
Indicates that something is obtained, acquired, or derived as a result of a specified source or cause.
-
E.
commercialOutcome
Indicates that an action, event, or relationship results in, or is associated with, a specific commercial or financial consequence.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:36 p.m.