Triple
T32002980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyulnyul people |
E817182
|
entity |
| Predicate | haveClanBasedSocialStructure |
P119075
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nyulnyul people, haveClanBasedSocialStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveClanBasedSocialStructure Context triple: [Nyulnyul people, haveClanBasedSocialStructure, true]
-
A.
hasSocialStructure
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
-
B.
clanOrSocietySystem
Indicates a relationship where a group is organized or structured according to a particular clan or society system.
-
C.
hasClanOrBandStructure
chosen
Indicates that an entity is organized into, or participates in, a social structure based on clans or bands.
-
D.
hasTribalCitizens
Indicates that one or more individuals are recognized as official members or citizens of a particular tribe.
-
E.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:14 a.m.