Triple
T5298467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanahuara District |
E119913
|
entity |
| Predicate | materialUsedInArchitecture |
P1272
|
FINISHED |
| Object | sillar (white 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: sillar (white volcanic stone) | Statement: [Yanahuara District, materialUsedInArchitecture, sillar (white volcanic stone)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialUsedInArchitecture Context triple: [Yanahuara District, materialUsedInArchitecture, sillar (white volcanic stone)]
-
A.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
C.
buildingMaterialTradition
Indicates the customary or historically established use of particular materials in the construction of a building or structure.
-
D.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
E.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.