Triple
T17470964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 木戸孝允 |
E425411
|
entity |
| Predicate | 関与した政策 |
P118077
|
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.
influencedPolicyArea
Indicates that one entity has affected, shaped, or guided the development, direction, or implementation of a particular policy area associated with another entity.
-
B.
linkedToPolicy
Indicates that an entity is associated or connected to a specific policy, such that the policy governs, influences, or is relevant to that entity.
-
C.
involvedPoliticalInstrument
chosen
Indicates that an entity participated in, utilized, or was otherwise engaged with a political tool, mechanism, or instrument as part of a political process or action.
-
D.
associatedPolis
Indicates a relationship where an entity is linked or connected to a particular city-state (polis), typically as its relevant or related political unit.
-
E.
relatedPoliticalProgram
Indicates that one political program is associated with, connected to, or contextually linked with another political program.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451abab908190b6d9d8a64f7c2ea3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.