Triple
T37379660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Aquatics Championships |
E928394
|
entity |
| Predicate | includesIndividualEvents |
P123434
|
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: [European Aquatics Championships, includesIndividualEvents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesIndividualEvents Context triple: [European Aquatics Championships, includesIndividualEvents, yes]
-
A.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
B.
multiEventsIncluded
Indicates that multiple distinct events are collectively contained within, or form part of, a larger event set or grouping.
-
C.
individualEvents
chosen
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
-
D.
isTeamEventIncluded
Indicates whether a particular team event is counted or considered as part of a specified set, schedule, or collection of events.
-
E.
includesActivities
Indicates that one entity contains, encompasses, or has as part of it the activities associated with another entity.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.