Triple
T38027867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamana clan |
E948828
|
entity |
| Predicate | opposedClanInOninWar |
P58168
|
FINISHED |
| Object | Hosokawa clan |
—
|
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: Hosokawa clan | Statement: [Yamana clan, opposedClanInOninWar, Hosokawa clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedClanInOninWar Context triple: [Yamana clan, opposedClanInOninWar, Hosokawa clan]
-
A.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
B.
clanStruggle
Indicates a conflict or power struggle occurring between different clans or clan-based groups.
-
C.
clanRival
chosen
Indicates a hostile or competitive relationship between two clans, typically involving ongoing conflict, opposition, or rivalry.
-
D.
wasEnemyOf
Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
-
E.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
- 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_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:20 p.m.