Triple
T18211279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kankiryo Saddle |
E436036
|
entity |
| Predicate | battlesOccurred |
P12233
|
FINISHED |
| Object | battles between Australian and Japanese forces |
—
|
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: battles between Australian and Japanese forces | Statement: [Kankiryo Saddle, battlesOccurred, battles between Australian and Japanese forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battlesOccurred Context triple: [Kankiryo Saddle, battlesOccurred, battles between Australian and Japanese forces]
-
A.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
B.
battleOccurredOn
chosen
Indicates that a specific battle took place at or on a particular location or date.
-
C.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
D.
numberOfMajorBattles
Indicates the total count of significant or major battles associated with an entity or event.
-
E.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e2296f8081908247a6dd08f99b25 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.