Triple
T9888163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tembo Deck |
E181387
|
entity |
| Predicate | separateTicketFromBase |
P91620
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tembo Deck, separateTicketFromBase, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separateTicketFromBase Context triple: [Tembo Deck, separateTicketFromBase, yes]
-
A.
ticketingCode
Indicates the specific fare or booking code associated with a ticket that defines its pricing, rules, and conditions of use.
-
B.
ticketOfTarget
Indicates that one entity is a ticket associated with, or issued for, a specific target entity.
-
C.
liftTicketType
Indicates the type or category of lift ticket associated with or assigned to an entity.
-
D.
ticket
Indicates that an entity serves as or is associated with a ticket, typically representing authorization, access, or a record for an event, service, or transaction.
-
E.
typicalTicketText
Indicates that the associated text represents the standard or commonly used wording for a ticket.
- F. None of above. chosen
Provenance (4 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4592db881909b134834dde614d8 |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:39 p.m.