Triple
T19639848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toconao |
E471500
|
entity |
| Predicate | hasTraditionalMaterial |
P50559
|
FINISHED |
| Object | volcanic stone |
—
|
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: volcanic stone | Statement: [Toconao, hasTraditionalMaterial, volcanic stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalMaterial Context triple: [Toconao, hasTraditionalMaterial, volcanic stone]
-
A.
traditionalMaterial
chosen
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
-
B.
hasTraditionalColors
Indicates that an entity is associated with colors that are traditionally or customarily linked to it.
-
C.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
D.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
E.
buildingMaterialTradition
Indicates the customary or historically established use of particular materials in the construction of a building or structure.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641215df48190926b38e6502bb83e |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.