Triple
T27913517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamkani |
E706003
|
entity |
| Predicate | borderlandIdentity |
P82254
|
FINISHED |
| Object | Afghanistan–Pakistan border 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: Afghanistan–Pakistan border tribes | Statement: [Chamkani, borderlandIdentity, Afghanistan–Pakistan border tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderlandIdentity Context triple: [Chamkani, borderlandIdentity, Afghanistan–Pakistan border tribes]
-
A.
borderlandsIdentity
chosen
Indicates a complex, hybrid sense of self that emerges in the cultural, social, or geographic margins where different groups, norms, or territories meet and overlap.
-
B.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
-
C.
borderStreet
Indicates that a street forms or lies along the boundary between two geographic areas or properties.
-
D.
realmBordered
Indicates that one realm shares a boundary or border with another realm.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 27, 2026, 6:51 p.m.