Triple
T15473399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I liga |
E376720
|
entity |
| Predicate | hasPlayOffsForPromotion |
P18796
|
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: [I liga, hasPlayOffsForPromotion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayOffsForPromotion Context triple: [I liga, hasPlayOffsForPromotion, yes]
-
A.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
-
B.
hasPlayOffs
chosen
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
C.
hasPromotionPlayoffs
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.
-
D.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
-
E.
hasRelegationPlayOff
Indicates that an entity is involved in or assigned to a relegation play-off match or series to determine its league status.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6c57308190b4cfe661c26addd4 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.