Triple
T5944724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebadea |
E132250
|
entity |
| Predicate | travelDestinationFor |
P21947
|
FINISHED |
| Object | consultation of the oracle |
—
|
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: consultation of the oracle | Statement: [Lebadea, travelDestinationFor, consultation of the oracle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelDestinationFor Context triple: [Lebadea, travelDestinationFor, consultation of the oracle]
-
A.
journeyDestination
chosen
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
B.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
C.
notableDestination
Indicates that a location is recognized as a significant or prominent place that people commonly travel to or aim to visit.
-
D.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
-
E.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.