Triple
T11164732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chao Phraya Express Boat |
E264130
|
entity |
| Predicate | ticketPurchaseLocation |
P43373
|
FINISHED |
| Object | piers |
—
|
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: piers | Statement: [Chao Phraya Express Boat, ticketPurchaseLocation, piers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketPurchaseLocation Context triple: [Chao Phraya Express Boat, ticketPurchaseLocation, piers]
-
A.
ticketingLocation
chosen
Indicates the place or point where tickets are issued, sold, or otherwise processed for an event, service, or journey.
-
B.
ticketPurchasedFrom
Indicates that a ticket was bought by one party from another party or source.
-
C.
ticketPurchaseMethod
Indicates the method or channel through which a ticket was purchased (e.g., online, in person, via mobile app).
-
D.
ticketMachines
Indicates that there is a relationship involving ticket machines, typically denoting where they are located, available, or associated with a particular entity or place.
-
E.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e887293081909830852000d533fa |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.