Triple
T12381352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NJC |
E295750
|
entity |
| Predicate | typeOfAppointmentPower |
P21124
|
FINISHED |
| Object | recommendatory, not directly appointive |
—
|
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: recommendatory, not directly appointive | Statement: [NJC, typeOfAppointmentPower, recommendatory, not directly appointive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAppointmentPower Context triple: [NJC, typeOfAppointmentPower, recommendatory, not directly appointive]
-
A.
typeOfPowerGranted
chosen
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
B.
typeOfPowerExercised
Indicates the specific kind or nature of power or authority that is being exercised in a given relationship or context.
-
C.
hasAppointmentAuthority
Indicates that an entity has the power or right to appoint another entity to a role, position, or responsibility.
-
D.
roleInAppointments
Indicates the specific function or capacity an entity holds within one or more scheduled appointments.
-
E.
appointmentPowerOver
Indicates that one entity has the authority to appoint, select, or assign another entity to a role, position, or function.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fbb3a2481908c2fcb5e6488eb3c |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.