Triple
T24274991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Army |
E605382
|
entity |
| Predicate | locationOfMainBattle |
P146580
|
FINISHED |
| Object | Sekigahara, Mino Province |
—
|
NE NERFINISHED |
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: Sekigahara, Mino Province | Statement: [Western Army, locationOfMainBattle, Sekigahara, Mino Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfMainBattle Context triple: [Western Army, locationOfMainBattle, Sekigahara, Mino Province]
-
A.
placeOfMainEngagement
Indicates the primary location where an entity carries out its main activities, operations, or engagements.
-
B.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
C.
primaryBattlefieldOf
chosen
Indicates that a specified location serves as the main or most significant battlefield where a particular conflict or war primarily took place.
-
D.
locationOfMajorDefeat
Indicates the place where a significant or decisive defeat of a party occurred.
-
E.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5eb3108190bbcd9fe1c091c365 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.