Triple
T218117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League |
E4152
|
entity |
| Predicate | promotionTo |
P8176
|
FINISHED |
| Object | N/A (top level) |
—
|
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: N/A (top level) | Statement: [Premier League, promotionTo, N/A (top level)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionTo Context triple: [Premier League, promotionTo, N/A (top level)]
-
A.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
B.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
C.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
D.
offersProgram
Indicates that an entity provides or makes available a specific program (such as a course, curriculum, or initiative).
-
E.
pushFactor
Indicates a driving influence or pressure that motivates or forces an entity to move away from, leave, or change its current situation or state.
- F. None of above. chosen
Provenance (4 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c5062e48190833be10e4770e1e9 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25be349588190aedde33d80682344 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.