Triple
T29583998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirifle |
E753670
|
entity |
| Predicate | hasSubclans |
P121811
|
FINISHED |
| Object | multiple lineages and subclans |
—
|
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: multiple lineages and subclans | Statement: [Mirifle, hasSubclans, multiple lineages and subclans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubclans Context triple: [Mirifle, hasSubclans, multiple lineages and subclans]
-
A.
hasSubclan
chosen
Indicates that one clan contains or is composed of a smaller, subordinate clan within its structure.
-
B.
hasNotableSubtribe
Indicates that an entity (typically a larger tribal or ethnic group) includes a particular subtribe that is especially recognized or notable.
-
C.
hasSubChiefs
Indicates that an entity holds a chief position that has one or more subordinate chiefs reporting to it.
-
D.
hasClanMother
Indicates that an individual belongs to or is under the authority or lineage of a specific clan mother within a clan-based social structure.
-
E.
hasChiefClan
Indicates that one entity serves as the primary or leading clan associated with 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 28, 2026, 6:09 p.m.