Triple
T4775929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Avenue Local |
E106045
|
entity |
| Predicate | typicalStopType |
P25018
|
FINISHED |
| Object | underground stations |
—
|
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: underground stations | Statement: [Fourth Avenue Local, typicalStopType, underground stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStopType Context triple: [Fourth Avenue Local, typicalStopType, underground stations]
-
A.
hasStopType
chosen
Indicates that a stop or stopping point is classified as having a particular type or category of stop.
-
B.
typicalStallType
Indicates the usual or most common type or category of stall associated with an entity.
-
C.
stationType
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
D.
majorStop
Indicates that a location functions as a primary or significant stop along a route or service path, typically where vehicles regularly halt for boarding, alighting, or key operations.
-
E.
hasStopArea
Indicates that an entity is associated with or contains a specific stop area, such as a designated location where vehicles stop.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.