Triple
T36283112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuman |
E892993
|
entity |
| Predicate | tribalHierarchyLevel |
P181633
|
FINISHED |
| Object | subtribe |
—
|
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: subtribe | Statement: [Tuman, tribalHierarchyLevel, subtribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalHierarchyLevel Context triple: [Tuman, tribalHierarchyLevel, subtribe]
-
A.
tribalRank
Indicates the hierarchical status or level an individual holds within a tribe or tribal social structure.
-
B.
hasTribalLevel
chosen
Indicates that one entity is associated with, classified by, or assigned a particular tribal level or rank in a hierarchical tribal structure.
-
C.
tribalStatus
Indicates that an entity holds a particular affiliation, recognition, or classification with respect to a tribe or tribal community.
-
D.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
E.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.