Triple
T1970731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Plaza |
E42792
|
entity |
| Predicate | isTransferStation |
P15892
|
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: [Queens Plaza, isTransferStation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTransferStation Context triple: [Queens Plaza, isTransferStation, yes]
-
A.
isMajorStationOn
Indicates that a station serves as a primary or significant stop on a particular route or line.
-
B.
servesAsThroughStationFor
Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
-
C.
isTransportationHubCodeFor
Indicates that a given code uniquely identifies and represents a specific transportation hub, such as a station, airport, or terminal.
-
D.
interchangeStation
chosen
Indicates a station where passengers can transfer between different routes, lines, or modes of transportation.
-
E.
isTransportHubBetween
Indicates that a location functions as a central node facilitating transportation connections between two or more other places.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3d2836c8190a35cb6d8e2dd4bdf |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.