Triple
T24844666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson Heights–Roosevelt Avenue/74th Street station |
E621711
|
entity |
| Predicate | hasStationComplexType |
P47116
|
FINISHED |
| Object | multi-level station complex |
—
|
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: multi-level station complex | Statement: [Jackson Heights–Roosevelt Avenue/74th Street station, hasStationComplexType, multi-level station complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationComplexType Context triple: [Jackson Heights–Roosevelt Avenue/74th Street station, hasStationComplexType, multi-level station complex]
-
A.
hasStationTypeAt
Indicates that a specific type of station is present or assigned at a particular location or point.
-
B.
hasStationStructure
chosen
Indicates that an entity possesses or is associated with a particular station-related physical structure.
-
C.
hasStationFunction
Indicates that an entity serves in a particular functional role or capacity at a station.
-
D.
hasComponentStation
Indicates that an entity includes or is associated with a specific station as one of its component parts.
-
E.
hasStationCodeSystem
Indicates that an entity uses or is associated with a particular system for assigning or managing station codes.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:19 a.m.