Triple
T33197959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Room (Biltmore Hotel) |
E849817
|
entity |
| Predicate | isIndoorSpace |
P8552
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Gold Room (Biltmore Hotel), isIndoorSpace, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndoorSpace Context triple: [Gold Room (Biltmore Hotel), isIndoorSpace, true]
-
A.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
B.
hasIndoorArea
Indicates that an entity possesses or includes an area or space that is located indoors or within a building.
-
C.
indoorOrOutdoor
chosen
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
D.
indoorOutdoorRelation
Indicates a spatial relationship specifying whether something is located indoors, outdoors, or how it connects indoor and outdoor spaces.
-
E.
indoorSectionName
Indicates the specific named section or area within an indoor space to which an entity is related.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:29 a.m.