Triple
T34530433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peoria Rocket |
E886521
|
entity |
| Predicate | operatingRailroadReportingMark |
P18202
|
FINISHED |
| Object | CRI&P |
—
|
NE NERFINISHED |
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: CRI&P | Statement: [Peoria Rocket, operatingRailroadReportingMark, CRI&P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingRailroadReportingMark Context triple: [Peoria Rocket, operatingRailroadReportingMark, CRI&P]
-
A.
railroadCodeFor
chosen
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
B.
railroadClass
Indicates the classification or category of a railroad according to an established system (e.g., by size, revenue, or regulatory status).
-
C.
operatedOnRailroad
Indicates that an entity conducted operations or provided services on a railroad system.
-
D.
isRegionalFreightRailroad
Indicates that a railroad operates primarily as a freight carrier within a specific geographic region rather than on a national or long-distance network.
-
E.
railCarries
Indicates that a rail or railway system transports or conveys a specified entity from one place to another.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
Created at: May 1, 2026, 2:02 a.m.