Triple
T1022855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Railroad Administration |
E22076
|
entity |
| Predicate | relinquishedControlOn |
P4657
|
FINISHED |
| Object | 1920-03-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: 1920-03-01 | Statement: [United States Railroad Administration, relinquishedControlOn, 1920-03-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relinquishedControlOn Context triple: [United States Railroad Administration, relinquishedControlOn, 1920-03-01]
-
A.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
B.
leasedFrom
Indicates that one entity is renting or leasing something from another entity, which acts as the owner or lessor.
-
C.
surrenderEvent
chosen
Indicates an event in which one party yields or gives up control, rights, or resistance to another party.
-
D.
releaseContext
Indicates ending or relinquishing a previously established context or state associated with an interaction or process.
-
E.
reliefGranted
Indicates that a requested form of assistance, exemption, or remedy has been officially approved and provided.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7e0f8908190bfe0a4cd8b31dfed |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b72619cc8190932fdfa0c74dc055 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.