Triple
T30531934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Categoría Primera B |
E777028
|
entity |
| Predicate | hasPlayoffsForPromotion |
P65444
|
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: [Categoría Primera B, hasPlayoffsForPromotion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayoffsForPromotion Context triple: [Categoría Primera B, hasPlayoffsForPromotion, yes]
-
A.
hasPromotionPlayoffs
chosen
Indicates that an entity participates in or is eligible for promotion playoffs, typically a post-season competition to move up to a higher division or level.
-
B.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
-
C.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
-
D.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
E.
hasPlayoffRoundBefore
Indicates that one playoff round occurs earlier in the sequence than another playoff round within the same competition or season.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 29, 2026, 8:18 p.m.