Triple
T28031912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knockouts World Championship |
E708294
|
entity |
| Predicate | hasDivisionName |
P78353
|
FINISHED |
| Object | Knockouts |
—
|
NE NERFINISHED |
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: Knockouts | Statement: [Knockouts World Championship, hasDivisionName, Knockouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDivisionName Context triple: [Knockouts World Championship, hasDivisionName, Knockouts]
-
A.
hasDivisionNames
chosen
Indicates that an entity is associated with one or more names of its internal divisions or subunits.
-
B.
hasDivisionCode
Indicates that an entity is associated with a specific division identifier or code within an organizational or classification structure.
-
C.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
D.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
E.
hasDivisionRole
Indicates that an entity holds a specific role or position within a particular division of an organization.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 27, 2026, 8:17 p.m.