Triple
T34809087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan Peoples Party |
E1003446
|
entity |
| Predicate | hasCoChairman |
P78958
|
FINISHED |
| Object | Asif Ali Zardari |
E305504
|
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: Asif Ali Zardari | Statement: [Pakistan Peoples Party, hasCoChairman, Asif Ali Zardari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoChairman Context triple: [Pakistan Peoples Party, hasCoChairman, Asif Ali Zardari]
-
A.
hasCoChair
chosen
Indicates that an entity shares the role of chair (leadership or oversight position) jointly with another entity.
-
B.
hasCoChairFrom
Indicates that an entity has a co-chair whose affiliation or origin is from a specified source, organization, or group.
-
C.
hasChairmanIn
Indicates that an entity has a person serving as its chairman in a specified organization, location, or context.
-
D.
hasChairpersonOrgan
Indicates that an organization or body has a specific organ (such as a board or committee) that holds the role of chairperson.
-
E.
hasChairHolder
Indicates that an entity holds or occupies a specific chair position or role associated with another entity.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3779467aa48190a12ebb158d3ebeed |
completed | June 21, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.