Triple
T31750246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chachi people |
E810395
|
entity |
| Predicate | reasonForStiltHouses |
P191703
|
FINISHED |
| Object | protection from flooding |
—
|
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: protection from flooding | Statement: [Chachi people, reasonForStiltHouses, protection from flooding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForStiltHouses Context triple: [Chachi people, reasonForStiltHouses, protection from flooding]
-
A.
reasonForUndergroundHomes
Indicates the underlying cause or motivation for why homes are built or located underground.
-
B.
reasonForHabitation
Indicates that an entity resides or inhabits a place for a specified reason or purpose.
-
C.
hasMotiveForInhabitants
Indicates that an entity provides or embodies a reason, incentive, or justification for the actions, behaviors, or presence of its inhabitants.
-
D.
reasonForNewBuilding
Indicates the underlying cause, motivation, or justification for constructing a new building.
-
E.
perchingAbility
Indicates the ability of an entity to perch or rest stably on a surface or support.
- F. None of above. chosen
Provenance (4 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 30, 2026, 11:27 p.m.