Triple
T13139601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 植木枝盛 |
E312175
|
entity |
| Predicate | 時代的文脈 |
P83770
|
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.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
B.
historical era
chosen
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
C.
culturalContextOfWork
Indicates the cultural setting, traditions, or background within which a work was created, interpreted, or is meaningfully situated.
-
D.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
E.
historicalContextOfWriting
Indicates that one entity provides the historical circumstances, period, or background in which another entity (typically a text or document) was written.
- 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.