Triple
T3455822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macugnaga |
E72900
|
entity |
| Predicate | hasTraditionalBuildingMaterial |
P29245
|
FINISHED |
| Object | wood |
—
|
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 | Statement: [Macugnaga, hasTraditionalBuildingMaterial, wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalBuildingMaterial Context triple: [Macugnaga, hasTraditionalBuildingMaterial, wood]
-
A.
buildingMaterialTradition
chosen
Indicates the customary or historically established use of particular materials in the construction of a building or structure.
-
B.
hasStationBuildingMaterial
Indicates that a station’s building is constructed from, or primarily composed of, a specified material.
-
C.
traditionallyBuiltOver
Indicates that one entity has been constructed on top of another in a manner consistent with long-established or customary building practices.
-
D.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
hasFloorMaterial
Indicates that an entity’s floor is made of, covered with, or constructed from a specified material.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa77b9c81909376a5995cdaf6ac |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.