Triple
T35585365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anmatyerr people |
E1028338
|
entity |
| Predicate | haveCustom |
P183424
|
FINISHED |
| Object | kinship-based social organisation |
—
|
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: kinship-based social organisation | Statement: [Anmatyerr people, haveCustom, kinship-based social organisation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveCustom Context triple: [Anmatyerr people, haveCustom, kinship-based social organisation]
-
A.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
-
B.
hasCustomTerm
Indicates that an entity is associated with a user-defined or non-standard term specific to a particular context or configuration.
-
C.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
- F. None of above. chosen
Provenance (4 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.