Triple
T25393825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Ōgimachi |
E636236
|
entity |
| Predicate | recognizedWarlord |
P109086
|
FINISHED |
| Object | Toyotomi Hideyoshi |
—
|
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: Toyotomi Hideyoshi | Statement: [Emperor Ōgimachi, recognizedWarlord, Toyotomi Hideyoshi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedWarlord Context triple: [Emperor Ōgimachi, recognizedWarlord, Toyotomi Hideyoshi]
-
A.
warlordCharacter
chosen
Indicates that one entity plays the role or has the characteristics of a warlord in relation to another entity or within a given context.
-
B.
isWarHeroOf
Indicates that one entity is recognized as a war hero in relation to, or on behalf of, another entity (such as a country, group, or cause).
-
C.
preeminentWarlordLineage
Indicates that one entity descends from or belongs to a lineage recognized as the foremost or most dominant among warlords.
-
D.
recognizesAsWarrior
Indicates that one entity acknowledges or accepts another entity as a warrior.
-
E.
wargBond
Indicates a special bond or partnership between a warg and another entity, typically involving loyalty, cooperation, or shared purpose.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 1:49 p.m.