Triple
T5037147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 永野修身 |
E113452
|
entity |
| Predicate | 評価・論争 |
P1783
|
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.
fieldOfDebate
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
-
B.
inAcademicDebate
Indicates that one entity is engaged in a formal, scholarly argument or discussion with another entity, typically following academic norms and methods of reasoning.
-
C.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
D.
controversy
chosen
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
E.
debateTopic
Indicates that one entity serves as the subject or issue being discussed or argued about in a debate involving another entity.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73bb069c8190af86f1b2f95f3d95 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.