Triple
T3502186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower 2 |
E73993
|
entity |
| Predicate | hasTicketedEntryToObservationDeck |
P11682
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tower 2, hasTicketedEntryToObservationDeck, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketedEntryToObservationDeck Context triple: [Tower 2, hasTicketedEntryToObservationDeck, true]
-
A.
hasObservationDeckAccess
Indicates that an entity is permitted to enter or use an observation deck.
-
B.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
C.
ticketedAttraction
chosen
Indicates that access to the attraction requires a purchased ticket or paid admission.
-
D.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
E.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbef47988190b5b3fe2e452b9ac8 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.