Triple
T37879752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōnin |
E944837
|
entity |
| Predicate | eraSequenceInMuromachiPeriod |
P110498
|
FINISHED |
| Object | follows Bunshō |
—
|
LITERAL FINISHED |
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: follows Bunshō | Statement: [Ōnin, eraSequenceInMuromachiPeriod, follows Bunshō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraSequenceInMuromachiPeriod Context triple: [Ōnin, eraSequenceInMuromachiPeriod, follows Bunshō]
-
A.
eraSequenceWithinDynasty
Indicates that one historical era occurs in a specific ordered position relative to another era within the same dynasty.
-
B.
preModernJapaneseEraSequence
Indicates that one pre-modern Japanese era chronologically precedes another in the historical sequence of eras.
-
C.
eraSequence
chosen
Indicates that one era or time period directly follows or precedes another in a chronological sequence.
-
D.
eraSequenceInEasternWu
Indicates that one era chronologically follows another within the historical sequence of Eastern Wu.
-
E.
eraSequenceInEmperorLingReign
Indicates that one era directly follows another within the chronological sequence of Emperor Ling’s reign.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.