Triple
T6763355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawan |
E154649
|
entity |
| Predicate | traditionalHousingType |
P51641
|
FINISHED |
| Object | round thatched houses |
—
|
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: round thatched houses | Statement: [Dawan, traditionalHousingType, round thatched houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHousingType Context triple: [Dawan, traditionalHousingType, round thatched houses]
-
A.
traditionalHomeOf
Indicates that a place is historically or customarily regarded as the primary homeland or origin location of a particular group or culture.
-
B.
traditionalHousingRegion
Indicates the region where a group’s customary or historically established housing patterns are typically found.
-
C.
traditionalHomeEnd
Indicates the point or time at which a traditional home, household, or customary domestic arrangement comes to an end.
-
D.
typicalHouse
chosen
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
-
E.
traditionallyHouses
Indicates that one entity has historically or customarily served as the location or container for 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:12 p.m.