Triple
T23914359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironman World Championship course section |
E602039
|
entity |
| Predicate | eventDiscipline |
P6316
|
FINISHED |
| Object | marathon portion |
—
|
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: marathon portion | Statement: [Ironman World Championship course section, eventDiscipline, marathon portion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDiscipline Context triple: [Ironman World Championship course section, eventDiscipline, marathon portion]
-
A.
esportDiscipline
Indicates that one entity is a specific esports game or discipline in which the other entity participates or is involved.
-
B.
sportEventType
chosen
Indicates the specific kind or category of sport associated with a given sporting event.
-
C.
sportEvent
Indicates a relationship where an entity is involved in, associated with, or characterizes a competitive or organized sporting event.
-
D.
olympicEventType
Indicates the specific category or discipline of an event within the Olympic Games.
-
E.
sportEventTypeOrganized
Indicates that an entity organizes or is responsible for arranging a specific type of sports event.
- 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.