Triple
T9146621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Power Stadium |
E219472
|
entity |
| Predicate | pitchDimensionsUnit |
P75639
|
FINISHED |
| Object | metres |
—
|
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: metres | Statement: [King Power Stadium, pitchDimensionsUnit, metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pitchDimensionsUnit Context triple: [King Power Stadium, pitchDimensionsUnit, metres]
-
A.
pitchDimensions
Indicates the specific measurements or size parameters that define the extent or layout of a pitch or playing field.
-
B.
dimensionOfLength
chosen
Indicates that something represents or specifies a measurement along a single spatial extent (a length dimension).
-
C.
USUnit
Indicates that the associated quantity or measurement is expressed using United States customary units (e.g., feet, pounds, gallons) rather than other unit systems.
-
D.
unitUK
Indicates that one entity uses or is measured in a unit of measure that is specific to or standard within the United Kingdom.
-
E.
runwayLengthUnit
Indicates the unit of measurement used to express the length of a runway in the relationship.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca917914c8190b97ca9169bbd1e5e |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.