Triple
T11313005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elwood, Illinois |
E267888
|
entity |
| Predicate | transportationHubProximity |
P6208
|
FINISHED |
| Object | major rail facilities |
—
|
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: major rail facilities | Statement: [Elwood, Illinois, transportationHubProximity, major rail facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationHubProximity Context triple: [Elwood, Illinois, transportationHubProximity, major rail facilities]
-
A.
transportationNearby
chosen
Indicates that there is a transportation facility or service located close to the referenced entity.
-
B.
operatorOfNearestStation
Indicates that an entity is the organization or operator responsible for managing the station that is geographically closest to a given reference point or entity.
-
C.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
D.
hasNearbyTransportationCorridor
Indicates that an entity is located close to a significant transportation route or corridor, such as a road, railway, or transit line.
-
E.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c1b7dc81908d8cc768c47390d3 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.