Triple
T19246358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burton Albion F.C. |
E481267
|
entity |
| Predicate | formerGroundOpened |
P34366
|
FINISHED |
| Object | Eton Park opened in 1958 |
—
|
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: Eton Park opened in 1958 | Statement: [Burton Albion F.C., formerGroundOpened, Eton Park opened in 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerGroundOpened Context triple: [Burton Albion F.C., formerGroundOpened, Eton Park opened in 1958]
-
A.
formerGround
chosen
Indicates that an entity previously served as the ground or base for another entity but no longer holds that role.
-
B.
formerStationOnSiteOpened
Indicates that a former station located on the same site was opened at a specified time.
-
C.
laterOpenedTo
Indicates that one entity became accessible or available after another entity had already been opened or made accessible.
-
D.
hasOpenedFor
Indicates that one entity has performed or appeared as the opening act or preliminary participant for another entity, typically in an event or performance context.
-
E.
previouslyOpenedTo
Indicates that an entity had been accessible or available to another entity at some earlier time in the past.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2daacc8190b8af99dee51f238d |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.