Triple
T23914370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironman World Championship course section |
E602039
|
entity |
| Predicate | hostedSince |
P102436
|
FINISHED |
| Object | late 1970s in Kailua-Kona |
—
|
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: late 1970s in Kailua-Kona | Statement: [Ironman World Championship course section, hostedSince, late 1970s in Kailua-Kona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedSince Context triple: [Ironman World Championship course section, hostedSince, late 1970s in Kailua-Kona]
-
A.
hostedBySince
chosen
Indicates that one entity has been continuously hosted or accommodated by another entity starting from a specified point in time.
-
B.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
C.
hostedAfter
Indicates that one hosting event occurred later in time than another hosting event.
-
D.
hostedFirst
Indicates that one entity acted as the initial host for another entity, preceding any subsequent hosts.
-
E.
hasBeenHostedIn
Indicates that an event, show, or activity took place or was conducted at a particular location or venue in the past.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce97f694819087215ed9f18b290e |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:39 p.m.