Triple
T37318068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cincinnati Southern Railway |
E926392
|
entity |
| Predicate | historicalTraffic |
P203531
|
FINISHED |
| Object | passenger |
—
|
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: passenger | Statement: [Cincinnati Southern Railway, historicalTraffic, passenger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTraffic Context triple: [Cincinnati Southern Railway, historicalTraffic, passenger]
-
A.
touristTraffic
Indicates the level, flow, or intensity of tourists visiting or moving through a particular place or area.
-
B.
annualTraffic
Indicates the typical amount or volume of traffic associated with something over the course of a year.
-
C.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
D.
cargoTrafficRank
Indicates the relative position of an entity in an ordered list based on the volume or intensity of its cargo traffic.
-
E.
streetUsage
Indicates how a street is used or intended to be used, such as for traffic, pedestrians, parking, or other specific functions.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
| PDg | Predicate description generation | batch_6a019d12c1208190940abb0736c389b0 |
completed | May 11, 2026, 9:10 a.m. |
Created at: May 3, 2026, 4:16 p.m.