Triple
T28018253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 World Aquatics Championships |
E707609
|
entity |
| Predicate | hasCompetitionPoolLength |
P41060
|
FINISHED |
| Object | 50 metres |
—
|
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: 50 metres | Statement: [2013 World Aquatics Championships, hasCompetitionPoolLength, 50 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionPoolLength Context triple: [2013 World Aquatics Championships, hasCompetitionPoolLength, 50 metres]
-
A.
hasPoolLength
chosen
Indicates that an entity (such as a pool) has a specific measured length.
-
B.
hasCompetitorNumber
Indicates that an entity is associated with a specific competitor identification number used to distinguish it in a competitive context.
-
C.
hasCompetitionElement
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
-
D.
hasCompetitionScope
Indicates the extent or boundaries within which a competition, contest, or competitive activity is defined or applies.
-
E.
hasCompetitionContext
Indicates that an entity is associated with or occurs within a specific competitive setting, event, or environment.
- 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_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: April 27, 2026, 8:08 p.m.