Triple
T6743759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pershing Square station |
E154154
|
entity |
| Predicate | ticketBarriersLocation |
P8430
|
FINISHED |
| Object | mezzanine level |
—
|
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: mezzanine level | Statement: [Pershing Square station, ticketBarriersLocation, mezzanine level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketBarriersLocation Context triple: [Pershing Square station, ticketBarriersLocation, mezzanine level]
-
A.
ticketingLocation
Indicates the place or point where tickets are issued, sold, or otherwise processed for an event, service, or journey.
-
B.
fareControlLocation
chosen
Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
-
C.
typicalBarrierType
Indicates the usual or characteristic type of barrier associated with or used in a given context or situation.
-
D.
tourAccess
Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
-
E.
securityLocation
Indicates the place or area where security-related activities, measures, or responsibilities are situated or applied.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1b3b1448190a94b4b64f01af14a |
completed | March 27, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.