Triple
T28018188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Aquatics Championships |
E707608
|
entity |
| Predicate | disciplineIncludedSinceInaugural |
P164011
|
FINISHED |
| Object | diving |
—
|
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: diving | Statement: [World Aquatics Championships, disciplineIncludedSinceInaugural, diving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disciplineIncludedSinceInaugural Context triple: [World Aquatics Championships, disciplineIncludedSinceInaugural, diving]
-
A.
disciplineIncludedSinceInaugural
chosen
Indicates that a particular discipline has been part of the event or program continuously since its inaugural edition.
-
B.
disciplineFondée
Indicates that one discipline was founded, established, or created by another discipline or foundational field.
-
C.
disciplineCount
Indicates the number of disciplinary actions or incidents associated with an entity.
-
D.
hasDisciplineSystem
Indicates that an entity possesses or is governed by a particular system of rules, methods, or practices for maintaining discipline.
-
E.
disciplineStrength
Indicates the degree or intensity of self-control or disciplined behavior an entity exhibits in its actions or decisions.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:08 p.m.