Triple
T15834511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skydome |
E383951
|
entity |
| Predicate | hasTourElement |
P119832
|
FINISHED |
| Object | viewing of sinkhole area |
—
|
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: viewing of sinkhole area | Statement: [Skydome, hasTourElement, viewing of sinkhole area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourElement Context triple: [Skydome, hasTourElement, viewing of sinkhole area]
-
A.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
hasSubTour
Indicates that one tour, route, or itinerary is contained within or forms a component part of another larger tour.
-
C.
hasTourLeg
Indicates that a specific segment or leg is part of, or associated with, a larger tour or journey.
-
D.
hasTouringMember
Indicates that an entity has a member who participates in its tours or live performances, typically as part of a traveling lineup.
-
E.
hasTourHistoryWith
Indicates that two entities have previously participated together in one or more tours or touring events.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e673e08819080c3f55a225607c7 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.