Triple
T34167258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamagata Castle |
E876444
|
entity |
| Predicate | mainLordResidence |
P42531
|
FINISHED |
| Object | Mogami Yoshiaki |
—
|
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: Mogami Yoshiaki | Statement: [Yamagata Castle, mainLordResidence, Mogami Yoshiaki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLordResidence Context triple: [Yamagata Castle, mainLordResidence, Mogami Yoshiaki]
-
A.
laterLordHouse
Indicates that one entity serves as the later or subsequent lordly house associated with another entity, typically in a succession or lineage of houses.
-
B.
legendaryHomeOf
Indicates that a place is traditionally or mythically regarded as the home or origin of a particular figure, group, or entity.
-
C.
houseSeat
chosen
Indicates that a particular location or structure serves as the primary residence or official dwelling place for an entity.
-
D.
builtResidence
Indicates that one entity constructed or was responsible for constructing a residence for another entity or for itself.
-
E.
chiefHouse
Indicates that a particular house serves as the primary or leading residence associated with a given entity (such as a person, group, or organization).
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fdfb02481908656f80d4f801ddf |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.