Triple
T4416131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大田実 |
E94977
|
entity |
| Predicate | 歴史的意義 |
P4345
|
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
chosen
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.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
D.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
E.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3551afb448190a2ce2000193808ac |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.