Triple
T5002387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 摺鉢山 |
E112402
|
entity |
| Predicate | 関連戦闘の期間 |
P28865
|
FINISHED |
| Object | 1945年2月から3月にかけての硫黄島の戦い |
—
|
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: 1945年2月から3月にかけての硫黄島の戦い | Statement: [摺鉢山, 関連戦闘の期間, 1945年2月から3月にかけての硫黄島の戦い]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 関連戦闘の期間 Context triple: [摺鉢山, 関連戦闘の期間, 1945年2月から3月にかけての硫黄島の戦い]
-
A.
battleDuration
Indicates the length of time for which a particular battle or combat event lasts.
-
B.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
C.
battleDateRelation
Indicates the temporal relationship specifying on which date a particular battle or combat event took place.
-
D.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
-
E.
associatedWithBattle
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.