Triple
T36698590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pueblo Siona |
E906156
|
entity |
| Predicate | viviendaTípica |
P51641
|
FINISHED |
| Object | casas construidas en madera |
—
|
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: casas construidas en madera | Statement: [pueblo Siona, viviendaTípica, casas construidas en madera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viviendaTípica Context triple: [pueblo Siona, viviendaTípica, casas construidas en madera]
-
A.
typicalHouse
chosen
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
-
B.
traditionallyHouses
Indicates that one entity has historically or customarily served as the location or container for another entity.
-
C.
typicalAbode
Indicates the usual or characteristic place where an entity lives, resides, or is most commonly found.
-
D.
traditionalHomeOf
Indicates that a place is historically or customarily regarded as the primary homeland or origin location of a particular group or culture.
-
E.
territorialHouse
Indicates that one entity serves as the territorial house or primary physical base associated with another entity’s jurisdiction or domain.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7ebdea48190b0e7565e4e09ec9e |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.