Triple
T3640794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Stadium |
E77181
|
entity |
| Predicate | roofCoverage |
P13382
|
FINISHED |
| Object | covered seating bowl with open playing field |
—
|
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: covered seating bowl with open playing field | Statement: [Texas Stadium, roofCoverage, covered seating bowl with open playing field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofCoverage Context triple: [Texas Stadium, roofCoverage, covered seating bowl with open playing field]
-
A.
roofStatus
Indicates the current condition or state of a roof, such as whether it is intact, damaged, under repair, or replaced.
-
B.
roofFunction
chosen
Indicates the functional role or purpose that a roof serves in relation to the structure it covers.
-
C.
surfaceCover
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
-
D.
roofMaterialOriginal
Indicates the material that was originally used to construct the roof of a structure.
-
E.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc357c3308190bd8801d68244a53e |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.