Triple
T37879771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōnin |
E944837
|
entity |
| Predicate | usedInDatingBattleRecords |
P199452
|
FINISHED |
| Object | Ōnin War chronicles |
—
|
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: Ōnin War chronicles | Statement: [Ōnin, usedInDatingBattleRecords, Ōnin War chronicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDatingBattleRecords Context triple: [Ōnin, usedInDatingBattleRecords, Ōnin War chronicles]
-
A.
usedInBattle
Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
-
B.
associatedWithBattle
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
-
C.
battleDateRelation
Indicates the temporal relationship specifying on which date a particular battle or combat event took place.
-
D.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
E.
hasBattleFormat
Indicates that an entity is associated with, or conducted under, a particular battle or combat ruleset or format.
- F. None of above. chosen
Provenance (4 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69ff397d6a2081908fa8f62e8902421b |
completed | May 9, 2026, 1:41 p.m. |
Created at: May 3, 2026, 4:19 p.m.