Triple
T20775642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Silent Games |
E511346
|
entity |
| Predicate | hasCompetitionsIn |
P26034
|
FINISHED |
| Object | athletics |
—
|
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: athletics | Statement: [International Silent Games, hasCompetitionsIn, athletics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionsIn Context triple: [International Silent Games, hasCompetitionsIn, athletics]
-
A.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
B.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
C.
hasCompetitionElement
chosen
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
-
D.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
-
E.
hasCompetitionCategory
Indicates that an entity is associated with a specific category or division within a competition.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26b06ac81909aef3b0a0ad79a33 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.