Triple
T33020263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FATA Agencies |
E844888
|
entity |
| Predicate | hadCapitalForAdministration |
P151559
|
FINISHED |
| Object | Peshawar |
—
|
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: Peshawar | Statement: [FATA Agencies, hadCapitalForAdministration, Peshawar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCapitalForAdministration Context triple: [FATA Agencies, hadCapitalForAdministration, Peshawar]
-
A.
hasCapitalAdministered
Indicates that a specified capital city is responsible for administering or governing a particular territory or political entity.
-
B.
capitalAdministeredFrom
chosen
Indicates that the administrative functions of a capital are carried out from a specified location.
-
C.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
D.
hadLocalGovernmentForm
Indicates that an entity possessed or was organized under a particular form or system of local government.
-
E.
hasCountyAdministration
Indicates that an entity is governed, managed, or served by a specific county-level administrative authority.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.