Triple
T28018191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Aquatics Championships |
E707608
|
entity |
| Predicate | disciplineRenamedTo |
P164558
|
FINISHED |
| Object | artistic swimming |
—
|
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: artistic swimming | Statement: [World Aquatics Championships, disciplineRenamedTo, artistic swimming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disciplineRenamedTo Context triple: [World Aquatics Championships, disciplineRenamedTo, artistic swimming]
-
A.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
B.
renamingAuthority
Indicates that the subject has the authority or power to change the name or designation of the object.
-
C.
changesNameTo
Indicates that an entity alters its current name and adopts a new specified name.
-
D.
realmRenamedFrom
Indicates that a realm currently known by one name previously had a different name from which it was renamed.
-
E.
wasRenamedBackTo
Indicates that an entity, after having its name changed, was later restored to its previous or original name.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 8:08 p.m.