Triple
T25676576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nōhime |
E643821
|
entity |
| Predicate | fatherDomain |
P158978
|
FINISHED |
| Object | Mino Province |
—
|
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: Mino Province | Statement: [Nōhime, fatherDomain, Mino Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatherDomain Context triple: [Nōhime, fatherDomain, Mino Province]
-
A.
fatherFrom
Indicates a parental relationship where one entity is the biological or legal father of another entity.
-
B.
familyAuthority
Indicates that one entity holds recognized decision-making power or control over another within a family or household context.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
fatherBasedOn
Indicates a paternal relationship inferred from indirect or derived evidence rather than directly asserted.
-
E.
familyClass
Indicates that an entity belongs to, or is categorized within, a particular family grouping or class in a familial or taxonomic hierarchy.
- F. None of above. chosen
Provenance (4 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3712cc8190b6e851960cc7c9e9 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 7:39 p.m.