Triple
T38027868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamana clan |
E948828
|
entity |
| Predicate | leaderDuringOninWar |
P11563
|
FINISHED |
| Object | Yamana Sōzen |
—
|
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: Yamana Sōzen | Statement: [Yamana clan, leaderDuringOninWar, Yamana Sōzen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderDuringOninWar Context triple: [Yamana clan, leaderDuringOninWar, Yamana Sōzen]
-
A.
commanderInChiefDuringWar
Indicates that one entity served as the highest-ranking military leader (commander in chief) of another entity for the duration of a specified war.
-
B.
leaderDuring
Indicates that one entity serves as the leader of another entity during a specified time period.
-
C.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
D.
operatorDuringWar
Indicates that an entity operated or was active in its role during a time of war.
-
E.
belligerentLeader
chosen
Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:20 p.m.