Triple
T20009304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotswold vernacular architecture |
E494544
|
entity |
| Predicate | typicalChimneyFeature |
P77397
|
FINISHED |
| Object | prominent stone chimneys |
—
|
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: prominent stone chimneys | Statement: [Cotswold vernacular architecture, typicalChimneyFeature, prominent stone chimneys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalChimneyFeature Context triple: [Cotswold vernacular architecture, typicalChimneyFeature, prominent stone chimneys]
-
A.
hasChimneys
chosen
Indicates that one entity possesses or is equipped with one or more chimneys.
-
B.
chimneyStatus
Indicates the operational or physical condition of a chimney, such as whether it is functional, damaged, blocked, or inactive.
-
C.
hasChimneyCount
Indicates the number of chimneys that an entity possesses or is associated with.
-
D.
heightOfChimney
Indicates the vertical measurement of a chimney from its base to its top.
-
E.
hasFireplace
Indicates that one entity possesses or is equipped with a fireplace.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a81c5881909692fcaaf59a57c9 |
completed | April 20, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.