Triple
T28018214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Aquatics Championships |
E707608
|
entity |
| Predicate | featuresPoolEvents |
P195764
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [World Aquatics Championships, featuresPoolEvents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPoolEvents Context triple: [World Aquatics Championships, featuresPoolEvents, yes]
-
A.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
B.
featuresEventsFor
Indicates that something presents, highlights, or includes specific events as part of its content or offering.
-
C.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
-
D.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
E.
drivesEventsOf
Indicates a causal relationship where one entity initiates, controls, or is responsible for the occurrence and progression of certain events.
- 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_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69fde5d677b88190bc904e6df8617c18 |
completed | May 8, 2026, 1:32 p.m. |
Created at: April 27, 2026, 8:08 p.m.