Triple
T30307272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One-Eyed Dragon of Ōshu |
E770818
|
entity |
| Predicate | refersToPersonWithResidence |
P22499
|
FINISHED |
| Object | Sendai |
—
|
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: Sendai | Statement: [One-Eyed Dragon of Ōshu, refersToPersonWithResidence, Sendai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToPersonWithResidence Context triple: [One-Eyed Dragon of Ōshu, refersToPersonWithResidence, Sendai]
-
A.
referredPersonResidence
Indicates that the residence or home location of a person who has been referred (e.g., to a service, program, or organization) is being specified or recorded.
-
B.
hasResidenceIn
chosen
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
C.
namedAfterResidenceOf
Indicates that one entity is named after the place where another entity lives or has lived.
-
D.
hasResidenceOn
Indicates that one entity’s place of residence is located on or along another entity, such as a street, road, or other linear feature.
-
E.
residesUnder
Indicates that one entity lives or is situated beneath another entity in a hierarchical or spatial structure.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 7:49 p.m.