Triple
T18666344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Murano |
E456333
|
entity |
| Predicate | hasUnitFeature |
P132207
|
FINISHED |
| Object | floor-to-ceiling windows |
—
|
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: floor-to-ceiling windows | Statement: [The Murano, hasUnitFeature, floor-to-ceiling windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnitFeature Context triple: [The Murano, hasUnitFeature, floor-to-ceiling windows]
-
A.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
B.
hasUnitStructure
Indicates that an entity possesses a specific internal organization or arrangement that defines its structural composition.
-
C.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
D.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
E.
hasBasicUnit
Indicates that one entity is composed of, defined by, or fundamentally characterized through another entity that serves as its basic or minimal unit.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556ad88b481908bd008d469e878fd |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.