Triple
T222657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central American Cup |
E4249
|
entity |
| Predicate | knockoutRounds |
P2703
|
FINISHED |
| Object | quarter-finals |
—
|
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: quarter-finals | Statement: [Central American Cup, knockoutRounds, quarter-finals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knockoutRounds Context triple: [Central American Cup, knockoutRounds, quarter-finals]
-
A.
competitionStage
chosen
Indicates the specific phase or round within a broader competition in which the related entities participate or are situated.
-
B.
draftRound
Indicates the specific round in which an entity was selected during a drafting or selection process.
-
C.
loserElimination
Indicates that the entity identified as the loser in a competition, game, or contest is removed or disqualified from further participation.
-
D.
playoffStructure
Indicates how a competition’s postseason phase is organized, including the format, seeding, and progression of teams or players through playoff rounds.
-
E.
playoffAppearances
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c705fd88190bfee7f5e1f7cee17 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5617788190814358aee3f7ae37 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.