Triple
T11671204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotswold stone |
E277381
|
entity |
| Predicate | typicalRoofForm |
P73260
|
FINISHED |
| Object | stone slate roofs |
—
|
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: stone slate roofs | Statement: [Cotswold stone, typicalRoofForm, stone slate roofs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRoofForm Context triple: [Cotswold stone, typicalRoofForm, stone slate roofs]
-
A.
roofTypeTypical
Indicates that a specified roof type is the common or characteristic roof style typically found for a given context or entity.
-
B.
hasTypeOfRoof
Indicates that an entity possesses or is characterized by a specific kind or style of roof.
-
C.
hasRoofShape
chosen
Indicates that one entity possesses or is characterized by a specific shape or form of roof.
-
D.
roofOptions
Indicates the available types or configurations of roofs that can be selected or applied to an entity.
-
E.
hasIconicRoofShape
Indicates that an entity possesses a roof with a distinctive, widely recognized, or characteristic shape.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a44264c08190ba1a4a5bcdc9367b |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.