Triple
T27796498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnden Park |
E702124
|
entity |
| Predicate | leagueEra |
P127432
|
FINISHED |
| Object | hosted top-flight and lower-division matches |
—
|
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: hosted top-flight and lower-division matches | Statement: [Burnden Park, leagueEra, hosted top-flight and lower-division matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueEra Context triple: [Burnden Park, leagueEra, hosted top-flight and lower-division matches]
-
A.
notableLeagueEra
Indicates that the subject is significantly associated with, or best known for participating in, a particular era or period of a sports league.
-
B.
leagueParticipationEra
Indicates the time period or era during which an entity participated in a particular league.
-
C.
associatedWithPlayerEra
Indicates a relationship where something is linked or connected to a specific era or period in a player's career.
-
D.
teamDivisionOrEra
Indicates the specific division or historical era within which a team is categorized or competed.
-
E.
associatedWithTeamEra
chosen
Indicates a relationship where an entity is linked to a specific period or era of a team’s history or existence.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 5:31 p.m.