Triple
T24275014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Army (Battle of Sekigahara) |
E605383
|
entity |
| Predicate | alsoCommandedBy |
P51109
|
FINISHED |
| Object | Tokugawa Hidetada |
—
|
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: Tokugawa Hidetada | Statement: [Eastern Army (Battle of Sekigahara), alsoCommandedBy, Tokugawa Hidetada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoCommandedBy Context triple: [Eastern Army (Battle of Sekigahara), alsoCommandedBy, Tokugawa Hidetada]
-
A.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
B.
associatedCommand
Indicates a relationship where one entity is linked to, or meant to be used with, a particular command or set of commands.
-
C.
coCommandedWith
chosen
Indicates that two or more entities shared command authority together over the same unit, operation, or context during a given period.
-
D.
commandedAs
Indicates that one entity held authority over another and issued orders or directives to be carried out.
-
E.
commandedByFrom
Indicates that an entity is under the authority or control of another entity originating from a specified source or location.
- 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.