Triple
T882495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CADE Estate Winery |
E19056
|
entity |
| Predicate | buildingFeature |
P16907
|
FINISHED |
| Object | eco-friendly estate design |
—
|
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: eco-friendly estate design | Statement: [CADE Estate Winery, buildingFeature, eco-friendly estate design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingFeature Context triple: [CADE Estate Winery, buildingFeature, eco-friendly estate design]
-
A.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
B.
buildingSection
Indicates a relationship where one entity is a specific section, part, or subdivision of a larger building.
-
C.
architectureProperty
chosen
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
D.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
E.
buildingShape
Indicates the geometric form or outline that characterizes a building’s overall structure.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4accc863c8190be9e5350732c30b1 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8eca748190b58e0f08b30fba43 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.