Triple
T22454770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost City |
E555085
|
entity |
| Predicate | ticketAccess |
P70950
|
FINISHED |
| Object | included in Trans Studio Makassar admission |
—
|
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: included in Trans Studio Makassar admission | Statement: [Lost City, ticketAccess, included in Trans Studio Makassar admission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketAccess Context triple: [Lost City, ticketAccess, included in Trans Studio Makassar admission]
-
A.
ticketingContext
Indicates the situational or operational context in which a ticket (such as a support, event, or issue ticket) is created, managed, or applied.
-
B.
ticketIncludes
chosen
Indicates that a particular ticket grants access to, contains, or covers the specified item, service, or component.
-
C.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
D.
ticketingScope
Indicates the range or domain within which ticketing actions (such as creation, assignment, or management of tickets) are valid or applicable.
-
E.
ticketReservation
Indicates the act of securing one or more tickets in advance for a specific event, service, or journey.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4e2bd4819083e5bed44e9776c6 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.