Triple
T1290613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wembley Stadium |
E27536
|
entity |
| Predicate | hasPitchDimensionsMetres |
P10736
|
FINISHED |
| Object | 105 x 68 |
—
|
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: 105 x 68 | Statement: [Wembley Stadium, hasPitchDimensionsMetres, 105 x 68]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPitchDimensionsMetres Context triple: [Wembley Stadium, hasPitchDimensionsMetres, 105 x 68]
-
A.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
B.
hasNationalDimension
Indicates that something possesses a scope, relevance, or impact at the level of a nation or entire country.
-
C.
hasStandardizedDimensions
Indicates that an entity conforms to a predefined, uniform set of measurements or size specifications.
-
D.
hasMeasurement
chosen
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
E.
heightInCentimetres
Indicates the numerical value of an entity’s height measured in centimetres.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d6af908190ade9c481cc6f0ad8 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.