Triple
T5528544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFL |
E144987
|
entity |
| Predicate | rebrandedAsEFL |
P41172
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [EFL, rebrandedAsEFL, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebrandedAsEFL Context triple: [EFL, rebrandedAsEFL, 2016]
-
A.
rebrandedToEFL
chosen
Indicates that an entity previously known by another name or brand was renamed or rebranded to the English Football League (EFL).
-
B.
announcedRebrandingAs
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of another entity.
-
C.
englishFlagship
Indicates that an entity participates in or is associated with an English flagship program (typically an intensive, advanced English language or studies track).
-
D.
focusAfterRebrand
Indicates that an entity’s primary emphasis, strategy, or positioning is considered in the period following a rebranding effort.
-
E.
languageIntroduced
Indicates that a particular language was brought into use or made known within a certain context, time, or place.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f8b6c348190b7d414dc1907d09a |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.