Triple
T28907103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 World Aquatics Championships |
E733111
|
entity |
| Predicate | openWaterDistanceUnit |
P145577
|
FINISHED |
| Object | kilometres |
—
|
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: kilometres | Statement: [2011 World Aquatics Championships, openWaterDistanceUnit, kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openWaterDistanceUnit Context triple: [2011 World Aquatics Championships, openWaterDistanceUnit, kilometres]
-
A.
hasDistanceUnit
chosen
Indicates that a specified unit of measurement is used to express a distance value in the relationship.
-
B.
typicalRaceDistanceUnit
Indicates the standard unit of measurement used to express the usual race distance associated with an entity.
-
C.
distancePerSwimmer
Indicates the amount of distance associated with or covered by each individual swimmer.
-
D.
approximateDistanceUnit
Indicates that the distance value is expressed in an approximate or non-exact unit of measurement.
-
E.
distanceMeasurementMethod
Indicates the method or technique used to determine or measure the distance between entities.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65adbd0c481909b11c92ac9aebea4 |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:08 a.m.