Triple
T22490373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Birmingham Road End |
E555999
|
entity |
| Predicate | relativeLocationInStadium |
P95425
|
FINISHED |
| Object | one end of the pitch |
—
|
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: one end of the pitch | Statement: [The Birmingham Road End, relativeLocationInStadium, one end of the pitch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLocationInStadium Context triple: [The Birmingham Road End, relativeLocationInStadium, one end of the pitch]
-
A.
relativePositionInStadium
chosen
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
B.
locatedInStadium
Indicates that an entity is situated within or at the premises of a specific stadium.
-
C.
locationInPlay
Indicates that an entity is currently situated or active within the defined play area or game environment.
-
D.
relativePositionWithinTeam
Indicates the positional or hierarchical relationship an entity holds relative to other members within the same team.
-
E.
associatedWithStadiumLocation
Indicates a relationship where an entity is connected or linked to the location of a specific stadium.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c40930c81908310ac6afd98c62e |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.