Triple
T321050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Skyliner |
E6415
|
entity |
| Predicate | usesTicketing |
P5937
|
FINISHED |
| Object | no separate fare required |
—
|
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: no separate fare required | Statement: [Disney Skyliner, usesTicketing, no separate fare required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTicketing Context triple: [Disney Skyliner, usesTicketing, no separate fare required]
-
A.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
B.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
C.
hasTicketRequirement
chosen
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
D.
usesFareMedium
Indicates that an entity employs a particular fare medium (such as a ticket, card, or pass) as the method of payment or validation for a trip or service.
-
E.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea8047c08190872c875e00f6e7dd |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e946607081909c8b97473aaf8d1b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.