Triple
T27945100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliamentary Committee of Pakistan |
E700858
|
entity |
| Predicate | appointmentFunction |
P137313
|
FINISHED |
| Object | scrutiny of nominees |
—
|
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: scrutiny of nominees | Statement: [Parliamentary Committee of Pakistan, appointmentFunction, scrutiny of nominees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointmentFunction Context triple: [Parliamentary Committee of Pakistan, appointmentFunction, scrutiny of nominees]
-
A.
appointmentBody
Indicates that one entity serves as the main content or body text associated with a particular appointment.
-
B.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
C.
appointmentContext
chosen
Indicates the situational details or circumstances under which an appointment occurs, such as purpose, setting, or relevant conditions.
-
D.
appointmentType
Indicates the specific category or nature of an appointment associated with an entity or event.
-
E.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
- 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_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 7:21 p.m.