Triple
T27179087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sawai people |
E683139
|
entity |
| Predicate | hasTraditionalHouseLocation |
P35447
|
FINISHED |
| Object | over water |
—
|
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: over water | Statement: [Sawai people, hasTraditionalHouseLocation, over water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalHouseLocation Context triple: [Sawai people, hasTraditionalHouseLocation, over water]
-
A.
hasTraditionalHouseStyle
Indicates that an entity possesses or is characterized by a traditional style of house or residential architecture.
-
B.
hasTraditionalResidenceType
Indicates that an entity is associated with a particular customary or historically established type of residence.
-
C.
hasAncestralResidence
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
D.
traditionallyHouses
chosen
Indicates that one entity has historically or customarily served as the location or container for another entity.
-
E.
hasTraditionalFarmBuildings
Indicates that an entity possesses or includes buildings typically associated with traditional farming activities.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 9:27 a.m.