Triple
T1765427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue People |
E38750
|
entity |
| Predicate | associatedWithSocialStructure |
P8216
|
FINISHED |
| Object | clan-based society |
—
|
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: clan-based society | Statement: [Blue People, associatedWithSocialStructure, clan-based society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSocialStructure Context triple: [Blue People, associatedWithSocialStructure, clan-based society]
-
A.
hasSocialStructure
chosen
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
-
B.
associatedWithSocialClass
Indicates a relationship in which an entity is linked or connected to a particular social class or socioeconomic stratum.
-
C.
associatedCommunity
Indicates a relationship where an entity is linked or connected to a particular community with which it is involved or identified.
-
D.
socialGroupInvolved
Indicates that a particular social group participates in, is affected by, or is otherwise involved in the specified event or situation.
-
E.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.