Triple
T24237300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Texans Ring of Honor |
E603118
|
entity |
| Predicate | locationOfDisplay |
P116310
|
FINISHED |
| Object | inside NRG Stadium bowl |
—
|
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: inside NRG Stadium bowl | Statement: [Houston Texans Ring of Honor, locationOfDisplay, inside NRG Stadium bowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfDisplay Context triple: [Houston Texans Ring of Honor, locationOfDisplay, inside NRG Stadium bowl]
-
A.
currentDisplayLocation
chosen
Indicates the location or context where something is presently being shown or rendered.
-
B.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
C.
devicePlacement
Indicates the spatial or positional arrangement of a device relative to its environment or other objects.
-
D.
locationPresented
Indicates that a specific location is presented or shown to an entity (such as a user or system) within a given context.
-
E.
uiLocation
Indicates the on-screen position or placement of a user interface element within a UI layout or display.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28a9c5c3081909cfddc8d29121817 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:03 a.m.