Triple
T8341772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zapatoca |
E195932
|
entity |
| Predicate | hasBuildingCharacteristic |
P6684
|
FINISHED |
| Object | whitewashed houses with clay tile roofs |
—
|
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: whitewashed houses with clay tile roofs | Statement: [Zapatoca, hasBuildingCharacteristic, whitewashed houses with clay tile roofs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingCharacteristic Context triple: [Zapatoca, hasBuildingCharacteristic, whitewashed houses with clay tile roofs]
-
A.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
B.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
C.
hasBuildingGrade
Indicates that a building is assigned a particular grade or quality rating.
-
D.
constructionCharacteristic
Indicates a specific structural or material property that characterizes how something is built or constructed.
-
E.
hasBuildingPattern
Indicates that an entity exhibits or follows a particular architectural or structural building pattern.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fe9efec81908e0c9ded3963bac5 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:58 p.m.