Triple
T17138091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laxsgiik |
E415890
|
entity |
| Predicate | clanStructureElement |
P126250
|
FINISHED |
| Object | composed of multiple house groups |
—
|
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: composed of multiple house groups | Statement: [Laxsgiik, clanStructureElement, composed of multiple house groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanStructureElement Context triple: [Laxsgiik, clanStructureElement, composed of multiple house groups]
-
A.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
B.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
C.
clanOrSocietySystem
Indicates a relationship where a group is organized or structured according to a particular clan or society system.
-
D.
clanChiefBranchOf
Indicates that a particular clan chief belongs to, or is a leading figure within, a specific branch or subdivision of a larger clan.
-
E.
clanSystemName
Indicates the name assigned to a clan within a clan-based system.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d1277881909325ffd2a7aa4873 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.