Triple
T13139593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 植木枝盛 |
E312175
|
entity |
| Predicate | 歴史的役割 |
P29914
|
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.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
B.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
C.
facedHistoricalImpact
Indicates that an entity has experienced or been subjected to a significant influence, consequence, or change resulting from historical events or processes.
-
D.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
E.
hasHistoricalRoleAs
chosen
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b6a4348190b9922ed255759078 |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:09 p.m.