Triple
T28227448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Century Avenue Station |
E711625
|
entity |
| Predicate | handlesHighPassengerVolume |
P35231
|
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: [Century Avenue Station, handlesHighPassengerVolume, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesHighPassengerVolume Context triple: [Century Avenue Station, handlesHighPassengerVolume, true]
-
A.
hasHeavyPassengerTraffic
chosen
Indicates that an entity experiences a high volume of passenger movement or usage over a given period.
-
B.
handlesMostPassengerTrafficOf
Indicates that one entity is responsible for managing the largest share of passenger traffic associated with another entity, compared to all similar entities.
-
C.
hasPassengerHandling
Indicates that an entity is responsible for or involved in managing the processes and services related to handling passengers.
-
D.
handlesCargoTraffic
Indicates that an entity is responsible for managing or processing the movement of cargo traffic.
-
E.
hasNumberOfSeatsAtPeak
Indicates the maximum number of seats available or occupied at the peak usage or capacity of something.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 10:50 p.m.