Triple
T36062715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yugiri |
E1043130
|
entity |
| Predicate | hasPutativeFather |
P46317
|
FINISHED |
| Object | Hikaru Genji |
—
|
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: Hikaru Genji | Statement: [Yugiri, hasPutativeFather, Hikaru Genji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPutativeFather Context triple: [Yugiri, hasPutativeFather, Hikaru Genji]
-
A.
hasPossibleFather
chosen
Indicates a relationship where a given individual may be the father of another, but this parentage is not confirmed.
-
B.
hasHolderFather
Indicates that an entity has a father who serves as the holder or custodian of that entity.
-
C.
geneticFatherOf
Indicates that one individual is the biological male parent (father) of another individual.
-
D.
possibleFatherInLaw
Indicates that one person is a potential or candidate father-in-law of another, typically as the (possible) father of that person’s spouse or prospective spouse.
-
E.
hasUncertainParentage
Indicates that the parent or parents of an entity are unknown, disputed, or not reliably established.
- 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.