Triple
T3463445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nari Nari people |
E73080
|
entity |
| Predicate | hasClanStructure |
P15952
|
FINISHED |
| Object | family-based groups along the river |
—
|
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: family-based groups along the river | Statement: [Nari Nari people, hasClanStructure, family-based groups along the river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanStructure Context triple: [Nari Nari people, hasClanStructure, family-based groups along the river]
-
A.
hasClanStatus
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
-
B.
hasClanSeat
Indicates that an entity holds an official seat or position within a particular clan.
-
C.
hasClanChiefStatus
Indicates that an entity holds the role or status of being the chief or leader of a clan.
-
D.
clanSystem
chosen
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
E.
hasSocialStructure
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb0b73f481908c9f8d2b9b9bbbaf |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.