Triple
T14224656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Aquatics Championships 2023 |
E352585
|
entity |
| Predicate | governingBodyRenamedIn |
P27966
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [World Aquatics Championships 2023, governingBodyRenamedIn, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyRenamedIn Context triple: [World Aquatics Championships 2023, governingBodyRenamedIn, 2023]
-
A.
governingBodyLaterKnownAs
chosen
Indicates that the governing body of an entity was later renamed or became known by a different official title.
-
B.
governingBodyPreviouslyKnownAs
Indicates that the governing body currently associated with an entity was formerly known by a different name.
-
C.
governingBodyAfter
Indicates that one governing body succeeds another as the official authority over the same entity or jurisdiction.
-
D.
governmentalBodyReformed
Indicates that an existing governmental body has been reorganized, restructured, or otherwise formally reformed.
-
E.
governanceChange
Indicates a change in the structure, rules, or authority of how an entity, organization, or system is governed.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6228e53c8190abbe4e2d88a7362a |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:06 a.m.