Triple
T875177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honcharuk Government |
E18900
|
entity |
| Predicate | hasPrimeMinisterAgeAtAppointment |
P6808
|
FINISHED |
| Object | 35 |
—
|
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: 35 | Statement: [Honcharuk Government, hasPrimeMinisterAgeAtAppointment, 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimeMinisterAgeAtAppointment Context triple: [Honcharuk Government, hasPrimeMinisterAgeAtAppointment, 35]
-
A.
ageAtFirstBecomingPrimeMinister
chosen
Indicates the age a person was when they first assumed the office of prime minister.
-
B.
primeMinisterTermStart
Indicates the date on which an individual officially begins serving as prime minister.
-
C.
primeMinisterAtEnactment
Indicates that the referenced person was serving as prime minister at the time a particular law, act, or measure was enacted.
-
D.
associatedPrimeMinister
Indicates that there is a relationship linking an entity (such as an event, organization, or period) to the prime minister who is connected with or responsible for it.
-
E.
appointsPrimeMinister
Indicates that one entity has the authority to select and formally designate another entity to serve in the role of prime minister.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acae12948190923d31966c26a130 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.