Triple
T18521047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esch–Cummins Act |
E452582
|
entity |
| Predicate | returnedToControlOf |
P110013
|
FINISHED |
| Object | private railroad companies |
—
|
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: private railroad companies | Statement: [Esch–Cummins Act, returnedToControlOf, private railroad companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToControlOf Context triple: [Esch–Cummins Act, returnedToControlOf, private railroad companies]
-
A.
returnedToUSControl
Indicates that control or authority over an entity has been transferred back to the United States.
-
B.
endedControlOf
chosen
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
C.
returnedToActivity
Indicates that an entity has resumed a previously paused, stopped, or inactive activity or state.
-
D.
returnedToUse
Indicates that something previously inactive, unavailable, or discontinued has been put back into active use or operation.
-
E.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338db5e4819086503a2176dfe499 |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.