Triple
T6957885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBVA Compass Stadium |
E161291
|
entity |
| Predicate | fieldDimensions |
P7759
|
FINISHED |
| Object | 115 yards x 75 yards |
—
|
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: 115 yards x 75 yards | Statement: [BBVA Compass Stadium, fieldDimensions, 115 yards x 75 yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldDimensions Context triple: [BBVA Compass Stadium, fieldDimensions, 115 yards x 75 yards]
-
A.
pitchDimensions
Indicates the specific measurements or size parameters that define the extent or layout of a pitch or playing field.
-
B.
fieldSize
chosen
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
C.
flagDimensions
Indicates the specific measurements (such as height, width, or aspect ratio) that define the size of a flag.
-
D.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
-
E.
dimensions_km
Indicates the physical size or extent of something measured in kilometers, typically specifying one or more linear dimensions (e.g., length, width, height).
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dad240ac8190808014a5b4920b41 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.