Triple
T730144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsimshian |
E14812
|
entity |
| Predicate | socialStructureFeature |
P8216
|
FINISHED |
| Object | ranked lineages |
—
|
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: ranked lineages | Statement: [Tsimshian, socialStructureFeature, ranked lineages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStructureFeature Context triple: [Tsimshian, socialStructureFeature, ranked lineages]
-
A.
hasSocialStructure
chosen
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
-
B.
socialFeature
Indicates that one entity provides or participates in a social interaction capability or function involving other entities.
-
C.
socialSystem
Indicates a relationship where entities are organized into a structured set of social roles, norms, and interactions that govern their collective behavior.
-
D.
communalAspect
Indicates that something involves or emphasizes shared participation, ownership, or experience within a group or community.
-
E.
populationRole
Indicates the role or function that an entity has within a population or demographic context.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f9b7608190bf97c8418a26e632 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.