Triple
T27739979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebellion |
E701825
|
entity |
| Predicate | hasKnockoutsDivisionMatches |
P97034
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rebellion, hasKnockoutsDivisionMatches, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKnockoutsDivisionMatches Context triple: [Rebellion, hasKnockoutsDivisionMatches, yes]
-
A.
hasKnockoutStage
Indicates that an entity includes, reaches, or is associated with a knockout (elimination) stage in a competition or tournament.
-
B.
hasKnockoutStageDraw
Indicates that an event or competition includes a defined draw or bracket structure for its knockout stage matches.
-
C.
divisionalRoundIncluded
chosen
Indicates that the referenced entity includes or pertains to the divisional round stage within a larger competition or playoff structure.
-
D.
numberOfKnockouts
Indicates the total count of times an entity has defeated opponents by knockout.
-
E.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f636a3e420819088512ed116c3b34d |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:09 p.m.