Triple
T37209504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocean Suites |
E922260
|
entity |
| Predicate | lowerLevelContains |
P187971
|
FINISHED |
| Object | bedroom |
—
|
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: bedroom | Statement: [Ocean Suites, lowerLevelContains, bedroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerLevelContains Context triple: [Ocean Suites, lowerLevelContains, bedroom]
-
A.
upperLevelContains
Indicates that a higher-level or parent entity includes or encompasses one or more lower-level or subordinate entities within its scope or structure.
-
B.
lowerLevelUsedFor
Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
-
C.
containsLevel
Indicates that one entity includes or encompasses a specific level or layer within its structure or hierarchy.
-
D.
lowerLevelCurrentlyUsedFor
Indicates that a lower level or subordinate layer is presently being utilized for a particular purpose or function.
-
E.
lowerRealmIncludes
Indicates that a lower-level or more specific realm, domain, or scope contains or encompasses another entity within its boundaries.
- F. None of above. chosen
Provenance (4 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:15 p.m.