Triple
T35637656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovakia national athletics team |
E1029763
|
entity |
| Predicate | athletesCompeteInDiscipline |
P179726
|
FINISHED |
| Object | sprints |
—
|
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: sprints | Statement: [Slovakia national athletics team, athletesCompeteInDiscipline, sprints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: athletesCompeteInDiscipline Context triple: [Slovakia national athletics team, athletesCompeteInDiscipline, sprints]
-
A.
athletesCompeteUnder
Indicates that athletes participate in competitions governed by a particular organization, rule set, or authority.
-
B.
competedInDiscipline
Indicates that an entity took part in a competition or event within a specific discipline or category.
-
C.
inSportDiscipline
chosen
Indicates that an entity participates, competes, or is involved in a specific sport discipline or event.
-
D.
sportDisciplineScope
Indicates the specific sport discipline or category within which a given relationship, rule, or activity is defined or applies.
-
E.
hasOlympicDiscipline
Indicates that an entity (typically a sport) includes or is associated with a specific discipline as recognized in the Olympic Games.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.