Triple
T20168006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embrun |
E491876
|
entity |
| Predicate | Embrunman triathlon |
P138942
|
FINISHED |
| Object | held annually on or around August 15 |
—
|
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: held annually on or around August 15 | Statement: [Embrun, Embrunman triathlon, held annually on or around August 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Embrunman triathlon Context triple: [Embrun, Embrunman triathlon, held annually on or around August 15]
-
A.
GrandTour
Indicates a comprehensive, often extended journey or series of visits undertaken to explore multiple places, typically for cultural, educational, or experiential purposes.
-
B.
Höhepunkt
Indicates the climax or peak point reached within an event, process, or development.
-
C.
stageRace
Indicates that an event is a multi-stage race composed of several sequential segments or stages.
-
D.
raceDayIncludes
Indicates that a particular race day schedule or event set contains or encompasses a specific race or racing-related activity.
-
E.
trekDurationApprox
Indicates an approximate length of time that the trek is expected to take.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66845cb588190820c50eea0c40d83 |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:35 p.m.