Triple
T10905534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa do Nordeste |
E257558
|
entity |
| Predicate | hasHomeAndAwayKnockoutRounds |
P39328
|
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: [Copa do Nordeste, hasHomeAndAwayKnockoutRounds, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeAndAwayKnockoutRounds Context triple: [Copa do Nordeste, hasHomeAndAwayKnockoutRounds, yes]
-
A.
hasHomeAndAwayFormat
chosen
Indicates that a competition, match, or series is structured with both home and away legs or fixtures between the same opponents.
-
B.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
-
C.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
D.
hasKnockoutStage
Indicates that an entity includes, reaches, or is associated with a knockout (elimination) stage in a competition or tournament.
-
E.
hasKnockoutStageDraw
Indicates that an event or competition includes a defined draw or bracket structure for its knockout stage matches.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770656c288190828e71600bb0acd4 |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.