Triple
T107925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2024 Summer Olympics |
E2178
|
entity |
| Predicate | hasDisciplineCategory |
P2767
|
FINISHED |
| Object | team sports |
—
|
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: team sports | Statement: [2024 Summer Olympics, hasDisciplineCategory, team sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisciplineCategory Context triple: [2024 Summer Olympics, hasDisciplineCategory, team sports]
-
A.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
-
B.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
C.
offersDiscipline
Indicates that one entity provides or makes available a particular field of study, training, or area of specialization to another entity.
-
D.
hasClericalDiscipline
Indicates that an entity is subject to, or governed by, a particular set of clerical or religious disciplinary rules or practices.
-
E.
hasMajorCategory
chosen
Indicates that something is associated with or classified under a primary, overarching category.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25a1199ac8190ac65ffaaf45b4f5b |
completed | Feb. 28, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69a2563e7188819091e9a94e071991d7 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.