Triple
T27852145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afridi |
E703981
|
entity |
| Predicate | historicalAlliances |
P19658
|
FINISHED |
| Object | other Karlani Pashtun tribes |
—
|
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: other Karlani Pashtun tribes | Statement: [Afridi, historicalAlliances, other Karlani Pashtun tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalAlliances Context triple: [Afridi, historicalAlliances, other Karlani Pashtun tribes]
-
A.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
B.
historicallyAlliedWith
chosen
Indicates that two entities have been political, military, or strategic allies during some period in the past.
-
C.
historicalFaction
Indicates that an entity was a member of, associated with, or part of a particular faction or side in a historical context or conflict.
-
D.
historicalEnemies
Indicates that the entities have been enemies of each other over a significant period in history.
-
E.
historicalRelationsWith
Indicates a relationship where one entity has documented or recognized connections, interactions, or associations with another entity in the past.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 27, 2026, 6:11 p.m.