Triple
T27441831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samawa people |
E690956
|
entity |
| Predicate | traditionalHouseFunction |
P31237
|
FINISHED |
| Object | stilt granary house |
—
|
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: stilt granary house | Statement: [Samawa people, traditionalHouseFunction, stilt granary house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHouseFunction Context triple: [Samawa people, traditionalHouseFunction, stilt granary house]
-
A.
traditionalFunction
Indicates that an entity serves a customary or historically established role or purpose within a cultural or social context.
-
B.
houseFunction
chosen
Indicates the functional role or primary use that a house serves (e.g., residential, commercial, mixed-use).
-
C.
traditionalHomeOf
Indicates that a place is historically or customarily regarded as the primary homeland or origin location of a particular group or culture.
-
D.
traditionalHomeDay
Indicates that a particular day is associated with traditional home-related activities, customs, or observances.
-
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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 27, 2026, 12:45 p.m.