Triple
T6890348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenyah |
E159028
|
entity |
| Predicate | traditionalDwellingType |
P35447
|
FINISHED |
| Object | longhouse |
—
|
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: longhouse | Statement: [Kenyah, traditionalDwellingType, longhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDwellingType Context triple: [Kenyah, traditionalDwellingType, longhouse]
-
A.
traditionallyHouses
chosen
Indicates that one entity has historically or customarily served as the location or container for another entity.
-
B.
traditionalHomeOf
Indicates that a place is historically or customarily regarded as the primary homeland or origin location of a particular group or culture.
-
C.
traditionallyBuiltOver
Indicates that one entity has been constructed on top of another in a manner consistent with long-established or customary building practices.
-
D.
traditionalHomeEnd
Indicates the point or time at which a traditional home, household, or customary domestic arrangement comes to an end.
-
E.
traditionalHomeStand
Indicates that an entity plays or hosts its home games at a venue considered its traditional or long-standing home location.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d92d45f08190a730b3842c95b521 |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:23 p.m.