Triple
T1290612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wembley Stadium |
E27536
|
entity |
| Predicate | hasArchHeightMetres |
P26117
|
FINISHED |
| Object | 133 |
—
|
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: 133 | Statement: [Wembley Stadium, hasArchHeightMetres, 133]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchHeightMetres Context triple: [Wembley Stadium, hasArchHeightMetres, 133]
-
A.
architecturalHeight
Indicates the measured vertical extent of a structure based on its architectural design, typically from the lowest significant level to the highest architecturally integral point, excluding non-architectural elements like antennas or masts.
-
B.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
heightInCentimetres
Indicates the numerical value of an entity’s height measured in centimetres.
-
D.
estimatedHeightAtHipsInMeters
Indicates the estimated vertical height, measured in meters, of an entity at the level of its hips.
-
E.
sideArchHeight
chosen
Indicates the vertical height measurement of a side arch relative to a reference point or baseline.
- 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.