Triple
T6053649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mykhailo Fedorov |
E134853
|
entity |
| Predicate | hasImplementedPolicy |
P172
|
FINISHED |
| Object | digital ID in Ukraine |
—
|
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: digital ID in Ukraine | Statement: [Mykhailo Fedorov, hasImplementedPolicy, digital ID in Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImplementedPolicy Context triple: [Mykhailo Fedorov, hasImplementedPolicy, digital ID in Ukraine]
-
A.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
B.
implementedPolicy
chosen
Indicates that a particular policy has been put into effect or carried out by an entity.
-
C.
hasVisitorPolicy
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
-
D.
hasReferencePolicy
Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
-
E.
hasNotablePolicy
Indicates that an entity possesses a policy that is distinguished, significant, or otherwise noteworthy in its context.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056f92b408190b0075766aad315d6 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.