Triple
T16788266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond League |
E408034
|
entity |
| Predicate | featuresAthletesLevel |
P116444
|
FINISHED |
| Object | world-class athletes |
—
|
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: world-class athletes | Statement: [Diamond League, featuresAthletesLevel, world-class athletes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAthletesLevel Context triple: [Diamond League, featuresAthletesLevel, world-class athletes]
-
A.
competitionLevelOf
chosen
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
B.
featuresPlayer
Indicates that something includes or prominently presents a particular player as part of its content or composition.
-
C.
featuredCompetitionLevel
Indicates that a particular competition level is highlighted or given special prominence relative to other levels.
-
D.
representsSportLevel
Indicates that an entity participates in or is associated with a particular level or tier within a sport.
-
E.
hasAthlete
Indicates a relationship where an entity (such as a team, organization, or event) includes or is associated with one or more athletes.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21c49788190b9a2ca2101604f64 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.