Triple
T27945098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliamentary Committee of Pakistan |
E700858
|
entity |
| Predicate | overseesAppointmentType |
P81048
|
FINISHED |
| Object | constitutional office holders |
—
|
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: constitutional office holders | Statement: [Parliamentary Committee of Pakistan, overseesAppointmentType, constitutional office holders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesAppointmentType Context triple: [Parliamentary Committee of Pakistan, overseesAppointmentType, constitutional office holders]
-
A.
appointerType
chosen
Indicates the role or category of entity that has the authority to appoint another entity.
-
B.
appointmentType
Indicates the specific category or nature of an appointment associated with an entity or event.
-
C.
overseesServiceType
Indicates that one entity has responsibility for supervising, managing, or directing the provision or operation of a particular type of service.
-
D.
typeOfAppointmentBody
Indicates the specific category or kind of appointment being referenced or scheduled.
-
E.
appointmentsInvolve
Indicates that scheduled appointments include or engage specific participants, resources, or activities in the appointment event.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 7:21 p.m.