Triple
T6095724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayan people |
E135870
|
entity |
| Predicate | housingFeature |
P62698
|
FINISHED |
| Object | communal longhouse veranda |
—
|
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: communal longhouse veranda | Statement: [Kayan people, housingFeature, communal longhouse veranda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housingFeature Context triple: [Kayan people, housingFeature, communal longhouse veranda]
-
A.
houseTraitAssociation
chosen
Indicates an associative relationship between a house and a particular trait or characteristic attributed to it.
-
B.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
C.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
D.
homeFieldType
Indicates the type or category of field that serves as the primary or home venue associated with an entity.
-
E.
houseUse
Indicates how a house or dwelling is used or purposed (e.g., residential, commercial, mixed-use).
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a963bac8190bc0c33fef187875c |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.