Triple
T10069971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadlock Field |
E213593
|
entity |
| Predicate | hasLuxuryAreas |
P3754
|
FINISHED |
| Object | hospitality 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: hospitality suites | Statement: [Hadlock Field, hasLuxuryAreas, hospitality suites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuxuryAreas Context triple: [Hadlock Field, hasLuxuryAreas, hospitality suites]
-
A.
hasLuxurySuites
chosen
Indicates that an entity provides or contains high-end, premium-quality suites as part of its accommodations or offerings.
-
B.
isLuxuryHotel
Indicates that a hotel is classified as a luxury establishment, typically offering high-end amenities, services, and accommodations.
-
C.
hasLandmarkArea
Indicates that a specified area is designated as the landmark area associated with a particular entity or location.
-
D.
isAffluentArea
Indicates that a given area is characterized by high wealth, income levels, or overall economic prosperity.
-
E.
hasFamousDistrict
Indicates that an entity possesses or contains a district that is widely recognized or renowned.
- 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcffa045c8190a08db0bb74cb006a |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:58 p.m.