Triple
T24274963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Army |
E605381
|
entity |
| Predicate | notableAllyDefectionFromWesternArmy |
P125830
|
FINISHED |
| Object | Kobayakawa Hideaki |
—
|
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: Kobayakawa Hideaki | Statement: [Eastern Army, notableAllyDefectionFromWesternArmy, Kobayakawa Hideaki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAllyDefectionFromWesternArmy Context triple: [Eastern Army, notableAllyDefectionFromWesternArmy, Kobayakawa Hideaki]
-
A.
notableAlly
Indicates that one entity is recognized as a significant or distinguished ally of another entity.
-
B.
notableHumanAlly
chosen
Indicates that one entity is a human who is a significant or noteworthy ally of another entity.
-
C.
initiallyAlliedWith
Indicates that two entities start out in a state of alliance or cooperation at the beginning of a specified period or scenario.
-
D.
formerAllyOf
Indicates that an entity was once an ally of another entity but that alliance has since ended.
-
E.
notableCommanderOrAlly
Indicates that an entity is a significant military leader or important ally associated with another entity, such as a person, group, or organization.
- 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.