Triple
T5646421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EverBank Stadium |
E124394
|
entity |
| Predicate | hasOutdoorDesign |
P8618
|
FINISHED |
| Object | open-air stadium |
—
|
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: open-air stadium | Statement: [EverBank Stadium, hasOutdoorDesign, open-air stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorDesign Context triple: [EverBank Stadium, hasOutdoorDesign, open-air stadium]
-
A.
hasOutdoorFocus
Indicates a relationship where an entity is primarily concerned with, oriented toward, or specialized in outdoor environments, activities, or contexts.
-
B.
isOutdoor
chosen
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
exteriorFeature
Indicates a relationship where one entity serves as an external or outward-facing feature, element, or characteristic of another entity.
-
E.
hasExteriorStyle
Indicates that an entity possesses or is characterized by a particular exterior design or stylistic appearance.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022aa650c819088d9046b82fab631 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.