Triple
T35074440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classic Box |
E1011971
|
entity |
| Predicate | hasTypicalCladding |
P179410
|
FINISHED |
| Object | wood clapboard siding |
—
|
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: wood clapboard siding | Statement: [Classic Box, hasTypicalCladding, wood clapboard siding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalCladding Context triple: [Classic Box, hasTypicalCladding, wood clapboard siding]
-
A.
claddingName
chosen
Indicates the specific name or designation assigned to a cladding material or system used on a structure.
-
B.
hasTypicalFrontage
Indicates that something normally faces or fronts onto something else, such as a property having its usual frontage on a particular street or area.
-
C.
glazingType
Indicates the type or configuration of glazing (such as single, double, or special coatings) used in or applied to an element.
-
D.
typicalFinish
Indicates that an action, process, or event commonly or characteristically ends with a particular outcome or state.
-
E.
hasLiningMaterial
Indicates that one entity uses or contains another entity as the material forming its inner lining.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 3, 2026, 4:01 p.m.