Triple
T26940560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carp Castle |
E678500
|
entity |
| Predicate | wasDaimyoResidenceOf |
P108856
|
FINISHED |
| Object | Asano clan lords of Hiroshima Domain |
—
|
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: Asano clan lords of Hiroshima Domain | Statement: [Carp Castle, wasDaimyoResidenceOf, Asano clan lords of Hiroshima Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDaimyoResidenceOf Context triple: [Carp Castle, wasDaimyoResidenceOf, Asano clan lords of Hiroshima Domain]
-
A.
originatedAsDaimyoResidence
Indicates that something began its existence or function as the residence of a daimyo.
-
B.
daimyoResidence
chosen
Indicates that a location serves or served as the official residence of a daimyo (feudal lord).
-
C.
shogunalResidence
Indicates that one entity serves as the official residence or seat of authority for a shogun associated with another entity.
-
D.
successorAsDaimyoOfHikone
Indicates that one entity became the next daimyō (feudal lord) of Hikone, directly succeeding another in that position.
-
E.
notableDaimyo
Indicates that a person held the status of a daimyō and is recognized as particularly prominent or historically significant among daimyō.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620531e28819086ffe00757f9743e |
completed | May 2, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:18 a.m.