Triple
T5377106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago and North Western Railway Company |
E112986
|
entity |
| Predicate | operatedFreightService |
P5884
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chicago and North Western Railway Company, operatedFreightService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedFreightService Context triple: [Chicago and North Western Railway Company, operatedFreightService, true]
-
A.
freightOperatorOnCorridor
Indicates that a particular freight operator provides services or operates along a specified transport corridor.
-
B.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
C.
operatesService
chosen
Indicates that an agent runs, manages, or provides a particular service.
-
D.
isOnFreightRoute
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
-
E.
operatesInterCityServices
Indicates that an entity runs or provides transportation services connecting different cities.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.