Triple
T26968472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digital Agency (Japan) |
E679237
|
entity |
| Predicate | hasKeyPolicyArea |
P7262
|
FINISHED |
| Object | digital government |
—
|
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 government | Statement: [Digital Agency (Japan), hasKeyPolicyArea, digital government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyPolicyArea Context triple: [Digital Agency (Japan), hasKeyPolicyArea, digital government]
-
A.
hasKeyPolicy
Indicates that an entity is associated with a specific key management or access control policy governing how its keys may be used or managed.
-
B.
hasPolicyArea
chosen
Indicates that an entity (such as a policy, program, or initiative) is associated with or pertains to a specific policy area or domain.
-
C.
hasKeyPolicyContext
Indicates that a key is associated with a specific policy context that governs how it may be used, managed, or accessed.
-
D.
hasKeyReformArea
Indicates that an entity is associated with or involves a primary or central area of reform.
-
E.
hasPolicyStatus
Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 6:37 a.m.