Triple
T19792233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikasa-no-miya household |
E475441
|
entity |
| Predicate | hasHouseNameElement |
P41017
|
FINISHED |
| Object | no-miya |
—
|
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: no-miya | Statement: [Mikasa-no-miya household, hasHouseNameElement, no-miya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHouseNameElement Context triple: [Mikasa-no-miya household, hasHouseNameElement, no-miya]
-
A.
usesHouseName
Indicates that an entity refers to or identifies a house by a specific house name rather than (or in addition to) other identifiers such as a number or address.
-
B.
hasFamilyNameElement
Indicates that an entity has a specific component or segment that forms part of its family name.
-
C.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
D.
houseName
chosen
Indicates the specific name or designation assigned to a house.
-
E.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c37a3c819080f195d58adaaa7b |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.