Triple
T5218627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fullerton station |
E117813
|
entity |
| Predicate | isMajorTransitHub |
P36293
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fullerton station, isMajorTransitHub, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTransitHub Context triple: [Fullerton station, isMajorTransitHub, yes]
-
A.
isMajorTransportLinkIn
Indicates that a transport route or connection serves as a primary or significant transportation link within a specified area or region.
-
B.
hasTransportHub
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
-
C.
hasMajorRailwayStation
Indicates that a place contains or is served by a principal railway station that functions as a major hub for rail transport.
-
D.
isMajorStationOn
Indicates that a station serves as a primary or significant stop on a particular route or line.
-
E.
hasMajorTransportationRole
chosen
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a96d49c8190a58726a57edebdcc |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.