Triple
T34765521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobayakawa clan |
E1002200
|
entity |
| Predicate | switchedSidesAt |
P60050
|
FINISHED |
| Object | Battle of Sekigahara |
—
|
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: Battle of Sekigahara | Statement: [Kobayakawa clan, switchedSidesAt, Battle of Sekigahara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: switchedSidesAt Context triple: [Kobayakawa clan, switchedSidesAt, Battle of Sekigahara]
-
A.
switchedSidesIn
chosen
Indicates that an entity changed allegiance or affiliation from one side to another within a specified conflict, group, or context.
-
B.
switchesPlacesWith
Indicates that two entities exchange their respective positions or roles with each other.
-
C.
surrenderRepresentedSide
Indicates that one side in a conflict or negotiation formally yields or capitulates on behalf of another specified side.
-
D.
changedHands
Indicates that ownership or control of something has been transferred from one party to another.
-
E.
belligerentSideAfterCapture
Indicates the party or side that an entity belongs to after it has been captured in a conflict or competitive interaction.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.