Triple
T16277485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snipe clan |
E395170
|
entity |
| Predicate | socialStratificationRole |
P93630
|
FINISHED |
| Object | clan-based organization |
—
|
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 organization | Statement: [Snipe clan, socialStratificationRole, clan-based organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStratificationRole Context triple: [Snipe clan, socialStratificationRole, clan-based organization]
-
A.
socioeconomicRole
Indicates the social and economic position, function, or status an entity holds within a society or system.
-
B.
socialClassPosition
Indicates the relative social status or rank an entity holds within a social hierarchy or class structure.
-
C.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
D.
stratificationRole
chosen
Indicates the role or function an entity plays within a hierarchical or layered structure used to organize or classify elements.
-
E.
socialClassContext
Indicates the social class or socioeconomic background within which an action, relationship, or situation occurs or is interpreted.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2460f73648190b5c931f2ba2a09da |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.