Triple
T32266823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zintani networks |
E824308
|
entity |
| Predicate | hasPowerBaseType |
P112282
|
FINISHED |
| Object | tribal |
—
|
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: tribal | Statement: [Zintani networks, hasPowerBaseType, tribal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerBaseType Context triple: [Zintani networks, hasPowerBaseType, tribal]
-
A.
hasPowerBase
chosen
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
B.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
-
C.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
D.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
-
E.
hasTypeOfPowerRegulated
Indicates that one entity exercises a specific kind of power or authority that is subject to regulation or control by another entity or governing framework.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 1, 2026, 12:42 a.m.