Triple
T34882061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFL Championship |
E1006039
|
entity |
| Predicate | promotionPlacesViaPlayoffs |
P41171
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [EFL Championship, promotionPlacesViaPlayoffs, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionPlacesViaPlayoffs Context triple: [EFL Championship, promotionPlacesViaPlayoffs, 1]
-
A.
promotionPlacesPerSeason
Indicates the number of promotion spots available in a competition for each season.
-
B.
promotionPlayoffs
Indicates a relationship where an entity qualifies for or participates in playoff matches that determine promotion to a higher level or division.
-
C.
playoffVenue
Indicates the location or facility where a playoff game or playoff series is held.
-
D.
promotionPlayOffWith
Indicates a relationship where entities compete in or are involved together in a promotion play-off, typically determining advancement to a higher level or division.
-
E.
playOffPromotionPlaces
chosen
Indicates the number or set of league positions that qualify teams for participation in promotion play-off 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.