Triple
T33779906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allianz Field |
E865622
|
entity |
| Predicate | hasHospitalityFeature |
P22897
|
FINISHED |
| Object | premium suites |
—
|
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: premium suites | Statement: [Allianz Field, hasHospitalityFeature, premium suites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHospitalityFeature Context triple: [Allianz Field, hasHospitalityFeature, premium suites]
-
A.
hasHospitalityComponent
chosen
Indicates that something includes, involves, or is associated with a hospitality-related element, service, or function.
-
B.
hasPassengerAmenity
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
C.
hasParkFeature
Indicates that a park includes, contains, or is associated with a specific feature or amenity.
-
D.
hasDiningFeature
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
E.
hasHotelType
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:45 a.m.