Triple
T38027922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashikaga Yoshimi |
E948829
|
entity |
| Predicate | predecessorInClaim |
P21282
|
FINISHED |
| Object | Ashikaga Yoshinori |
—
|
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: Ashikaga Yoshinori | Statement: [Ashikaga Yoshimi, predecessorInClaim, Ashikaga Yoshinori]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInClaim Context triple: [Ashikaga Yoshimi, predecessorInClaim, Ashikaga Yoshinori]
-
A.
predecessorAsClaimant
chosen
Indicates that one entity previously held the status or role of claimant before another entity in a succession or sequence of claims.
-
B.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
-
C.
successorClaimant
Indicates that one entity is the next or replacement claimant to a right, title, or claim previously held by another entity.
-
D.
predecessorInRegency
Indicates that one regent directly preceded another in holding regency authority over the same domain or office.
-
E.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
- 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_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:20 p.m.