Triple
T26968418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 岸田文雄内閣 |
E679236
|
entity |
| Predicate | デジタル政策 |
P137107
|
FINISHED |
| Object | デジタル庁の活用 |
—
|
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: デジタル庁の活用 | Statement: [岸田文雄内閣, デジタル政策, デジタル庁の活用]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: デジタル政策 Context triple: [岸田文雄内閣, デジタル政策, デジタル庁の活用]
-
A.
digital
Indicates that the relationship or action occurs in, uses, or pertains to electronic or computer-based (non-physical) form or processes.
-
B.
digitalByDefault
Indicates that the primary or standard method for performing the related process, service, or interaction is through digital channels rather than physical or manual means.
-
C.
nationalPolicy
Indicates that an entity establishes, embodies, or is governed by an official policy at the level of a nation-state.
-
D.
technologyPolicy
chosen
Indicates a relationship where rules, guidelines, or strategies are established to govern the development, use, or impact of technology.
-
E.
hasDigitalInitiative
Indicates that an entity is engaged in or associated with a specific digital project, program, or transformation effort.
- 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_69f621233f2c81908c237f20c50c2ba3 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:37 a.m.