Triple
T34882060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFL Championship |
E1006039
|
entity |
| Predicate | promotionPlacesAutomatic |
P41170
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [EFL Championship, promotionPlacesAutomatic, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionPlacesAutomatic Context triple: [EFL Championship, promotionPlacesAutomatic, 2]
-
A.
promotionPlaces
Indicates that one entity designates or assigns another entity to a higher position, rank, or status within some organizational or hierarchical structure.
-
B.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
-
C.
automaticPromotionPlaces
chosen
Indicates the number or set of positions in a ranking or competition that result in automatic promotion to a higher level or division.
-
D.
nearestTouristDestination
Indicates that one location is the closest tourist destination to another specified location.
-
E.
targetedPlace
Indicates that an entity intentionally directed an action, operation, or influence toward a specific place or location.
- 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_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.