Triple
T37777207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enxaimel (half-timbered) style |
E941719
|
entity |
| Predicate | typicalInfillMaterial |
P104293
|
FINISHED |
| Object | masonry |
—
|
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: masonry | Statement: [Enxaimel (half-timbered) style, typicalInfillMaterial, masonry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInfillMaterial Context triple: [Enxaimel (half-timbered) style, typicalInfillMaterial, masonry]
-
A.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
usesSupportMaterial
Indicates that an entity relies on or incorporates additional supporting materials or resources to carry out an action or fulfill a function.
-
C.
suppliedMaterialType
Indicates the type or category of material that is provided or supplied in a given context.
-
D.
featuresMaterialType
chosen
Indicates that an entity is characterized by or incorporates a specific type of material.
-
E.
testedMaterial
Indicates that an entity has been used as the material or substance on which a test or experiment was performed.
- 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.