Triple
T38027880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamana clan |
E948828
|
entity |
| Predicate | declineBeganAfter |
P19208
|
FINISHED |
| Object | Ōnin War |
—
|
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 | Statement: [Yamana clan, declineBeganAfter, Ōnin War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declineBeganAfter Context triple: [Yamana clan, declineBeganAfter, Ōnin War]
-
A.
declineBeganInPeriod
Indicates that the onset of a decline in the subject occurred during the specified time period.
-
B.
declineAfter
chosen
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
C.
declineBeganUnder
Indicates that a period of decline started during the tenure, rule, or administration of a specified entity.
-
D.
declineOrEnd
Indicates that a relationship, process, or state is either decreasing in intensity or coming to a complete end.
-
E.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
- 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_69fbc99760d48190a5d0d00c36307456 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.