Triple
T33414721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orakzai tribe |
E855681
|
entity |
| Predicate | administrativeAreaNamedAfter |
P21562
|
FINISHED |
| Object | Orakzai District |
—
|
NE NERFINISHED |
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 District | Statement: [Orakzai tribe, administrativeAreaNamedAfter, Orakzai District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeAreaNamedAfter Context triple: [Orakzai tribe, administrativeAreaNamedAfter, Orakzai District]
-
A.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
B.
denotesAdministrativeArea
Indicates that one entity designates or specifies another entity as its relevant administrative area or jurisdiction.
-
C.
modernNameOfArea
Indicates that one area entity represents the current or modern name of another area entity.
-
D.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
E.
hasPlaceNamedAfter
chosen
Indicates that one place is named in honor of or derived from the name of another place.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 1, 2026, 1:36 a.m.