Triple
T25004377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Oaks Hotel |
E625799
|
entity |
| Predicate | outdoorAreaFeature |
P84779
|
FINISHED |
| Object | shaded seating under oak tree |
—
|
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: shaded seating under oak tree | Statement: [The Oaks Hotel, outdoorAreaFeature, shaded seating under oak tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outdoorAreaFeature Context triple: [The Oaks Hotel, outdoorAreaFeature, shaded seating under oak tree]
-
A.
hasOutdoorSpaceType
chosen
Indicates the specific kind of outdoor area associated with an entity, such as a balcony, terrace, garden, or patio.
-
B.
isOutdoorFacility
Indicates that a facility is located outdoors or primarily functions in an open-air environment.
-
C.
outdoorVenue
Indicates that an event, activity, or gathering takes place at a location situated outdoors rather than inside a building or enclosed structure.
-
D.
hasOutdoorType
Indicates that an entity is associated with a specific type or category of outdoor environment or feature.
-
E.
hasStandingArea
Indicates that an entity includes or provides a designated area where people can stand.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b0ee0388190a07b6c0bcd817af9 |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:05 a.m.