Triple
T7265307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English First Division title |
E159756
|
entity |
| Predicate | locationOfMatches |
P15860
|
FINISHED |
| Object | various club stadiums in England and Wales |
—
|
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: various club stadiums in England and Wales | Statement: [English First Division title, locationOfMatches, various club stadiums in England and Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfMatches Context triple: [English First Division title, locationOfMatches, various club stadiums in England and Wales]
-
A.
locationPattern
Indicates a recurring or structured spatial relationship, where an entity consistently appears or is arranged in a particular type of location or spatial configuration.
-
B.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
C.
matchdayLocation
Indicates the venue or place where a particular matchday or game is held.
-
D.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
E.
gameLocation
chosen
Indicates the place or venue where a game or match takes 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.