Triple
T1970730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Plaza |
E42792
|
entity |
| Predicate | fareControlArea |
P8430
|
FINISHED |
| Object | unified 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: unified station complex | Statement: [Queens Plaza, fareControlArea, unified station complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareControlArea Context triple: [Queens Plaza, fareControlArea, unified station complex]
-
A.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
B.
fareControlLocation
chosen
Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
-
C.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
D.
flightRules
Indicates the regulatory or procedural rules that govern how a flight must be conducted or operated.
-
E.
rangeAgainstAircraft
Indicates that one entity measures, determines, or engages the distance to an aircraft target.
- 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.