Triple
T36062719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yugiri |
E1043130
|
entity |
| Predicate | birthCircumstances |
P141778
|
FINISHED |
| Object | paternity disputed between Hikaru Genji and To no Chujo |
—
|
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: paternity disputed between Hikaru Genji and To no Chujo | Statement: [Yugiri, birthCircumstances, paternity disputed between Hikaru Genji and To no Chujo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthCircumstances Context triple: [Yugiri, birthCircumstances, paternity disputed between Hikaru Genji and To no Chujo]
-
A.
birthType
Indicates the manner or method by which a birth occurred or was brought about.
-
B.
birthProcess
Indicates the biological process through which a new organism is brought into existence from its parent or parents.
-
C.
birthNarrative
chosen
Indicates a narrative or account that describes the circumstances, events, or story surrounding an entity’s birth.
-
D.
birthStatus
Indicates the condition or circumstances of an entity’s birth, such as whether and how it was born.
-
E.
birthEvent
Indicates an event in which an entity comes into existence by being born, typically linking the newborn to contextual details such as time, place, and participants.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.