Triple
T37777213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enxaimel (half-timbered) style |
E941719
|
entity |
| Predicate | nonLoadBearingElement |
P186985
|
FINISHED |
| Object | infill walls |
—
|
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: infill walls | Statement: [Enxaimel (half-timbered) style, nonLoadBearingElement, infill walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonLoadBearingElement Context triple: [Enxaimel (half-timbered) style, nonLoadBearingElement, infill walls]
-
A.
nonMaterialAspect
Indicates that one entity represents an immaterial, intangible, or conceptual aspect or property of another entity.
-
B.
notStandalone
Indicates that an entity cannot exist, function, or be valid independently and must be associated with or supported by another entity.
-
C.
isNonCombustible
Indicates that the subject does not burn or support combustion under normal conditions.
-
D.
architecturalElements
chosen
Indicates a relationship where certain components or features function as structural or design elements within an architectural context.
-
E.
hasNotableStructureOn
Indicates that a subject entity possesses or features a significant or noteworthy structure located on it.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbaf443e5c8190bfaf3e00ced78a30 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.