Triple
T33414757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalaya |
E855682
|
entity |
| Predicate | locatedInTribalArea |
P9431
|
FINISHED |
| Object | Orakzai tribal area |
E241887
|
NE 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: Orakzai tribal area | Statement: [Kalaya, locatedInTribalArea, Orakzai tribal area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTribalArea Context triple: [Kalaya, locatedInTribalArea, Orakzai tribal area]
-
A.
includedTribalAreas
chosen
Indicates that certain areas are designated as tribal regions and are formally included within a specified jurisdiction, boundary, or administrative scope.
-
B.
locatedInUnionTerritory
Indicates that an entity is geographically situated within a specified union territory.
-
C.
locatedInAutonomousRegion
Indicates that one entity is geographically or administratively situated within a self-governing or semi-independent regional territory.
-
D.
tribalRegionOf
Indicates that one entity is the geographic region traditionally inhabited, controlled, or associated with a particular tribe.
-
E.
locatedInBorderDistrictOnIndianSide
Indicates that something is situated within a border district that lies on the Indian side of an international boundary.
- F. None of above.
Provenance (4 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35814d53288190bdacb516eb3b6d29 |
completed | June 19, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.