Triple
T29275267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission on Appointments |
E742227
|
entity |
| Predicate | typeOfAppointmentReviewed |
P117663
|
FINISHED |
| Object | heads of executive departments |
—
|
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: heads of executive departments | Statement: [Commission on Appointments, typeOfAppointmentReviewed, heads of executive departments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAppointmentReviewed Context triple: [Commission on Appointments, typeOfAppointmentReviewed, heads of executive departments]
-
A.
appointmentType
Indicates the specific category or nature of an appointment associated with an entity or event.
-
B.
typeOfAppointmentBody
chosen
Indicates the specific category or kind of appointment being referenced or scheduled.
-
C.
appointerType
Indicates the role or category of entity that has the authority to appoint another entity.
-
D.
typicalAppointment
Indicates that an appointment represents a standard, usual, or commonly occurring scheduling arrangement between entities.
-
E.
decisionTypeReviewed
Indicates that a particular decision has been examined or evaluated, typically as part of a review or oversight 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: April 28, 2026, 12:50 p.m.