Triple
T33020269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FATA Agencies |
E844888
|
entity |
| Predicate | governedDirectlyFrom |
P6175
|
FINISHED |
| Object | Islamabad |
—
|
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: Islamabad | Statement: [FATA Agencies, governedDirectlyFrom, Islamabad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedDirectlyFrom Context triple: [FATA Agencies, governedDirectlyFrom, Islamabad]
-
A.
governedFrom
chosen
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
-
B.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
C.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
D.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
E.
governedThrough
Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
- 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_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: May 1, 2026, 1:23 a.m.