Triple
T38088763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clann Shiosal |
E951049
|
entity |
| Predicate | usesClanSystemElement |
P28158
|
FINISHED |
| Object | clan chief |
—
|
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 chief | Statement: [Clann Shiosal, usesClanSystemElement, clan chief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClanSystemElement Context triple: [Clann Shiosal, usesClanSystemElement, clan chief]
-
A.
hasClanStatus
chosen
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
-
B.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
C.
hasClanOrBandStructure
Indicates that an entity is organized into, or participates in, a social structure based on clans or bands.
-
D.
isPrincipalClanOf
Indicates that one clan holds primary or leading status over another clan within a hierarchical or organizational structure.
-
E.
usesClanPraise
Indicates that one entity employs or invokes the traditional praise names or laudatory expressions associated with a particular clan in relation to another entity.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 3, 2026, 4:21 p.m.