Triple
T9633768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zarai Taraqiati Bank Limited |
E232871
|
entity |
| Predicate | hasBranchNetwork |
P68855
|
FINISHED |
| Object | nationwide in Pakistan |
—
|
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: nationwide in Pakistan | Statement: [Zarai Taraqiati Bank Limited, hasBranchNetwork, nationwide in Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchNetwork Context triple: [Zarai Taraqiati Bank Limited, hasBranchNetwork, nationwide in Pakistan]
-
A.
branchNetwork
Indicates that one entity operates as a branch or local outlet within the wider organizational or operational network of another entity.
-
B.
hasBranchOffice
chosen
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
-
C.
isPartOfBranchTypically
Indicates that something is typically a component or subdivision within a larger branch.
-
D.
hasTrailNetwork
Indicates that an entity possesses or is associated with a system of interconnected trails or paths.
-
E.
hadBranchIn
Indicates that an organization or entity maintained a branch, office, or subsidiary located in another specified place or entity.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b28ce2c819086d3c6e4e6ea95a7 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.