Triple
T32729693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KOK |
E836913
|
entity |
| Predicate | hasBeenInGovernmentOf |
P57154
|
FINISHED |
| Object | Finland |
—
|
NE NERFINISHED |
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: Finland | Statement: [KOK, hasBeenInGovernmentOf, Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenInGovernmentOf Context triple: [KOK, hasBeenInGovernmentOf, Finland]
-
A.
wasInGovernmentWith
Indicates that two individuals served together within the same government or administration during an overlapping period.
-
B.
servedInGovernmentWith
Indicates that two individuals held positions in the same government or administration during an overlapping period of time.
-
C.
hasBeenInGovernmentUntil
Indicates that an entity held a government position continuously up to a specified end time or date.
-
D.
workedUnderGovernmentOf
chosen
Indicates that an entity was employed by, served within, or operated under the authority of a specific government or its administrative bodies.
-
E.
servedInCabinetOf
Indicates that one person held a position as a member of the governmental cabinet led by another person.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:11 a.m.