Triple
T36062716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yugiri |
E1043130
|
entity |
| Predicate | hasPossibleBiologicalFather |
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, hasPossibleBiologicalFather, Hikaru Genji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPossibleBiologicalFather Context triple: [Yugiri, hasPossibleBiologicalFather, 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.
geneticFatherOf
Indicates that one individual is the biological male parent (father) of another individual.
-
C.
hasUncertainParentage
Indicates that the parent or parents of an entity are unknown, disputed, or not reliably established.
-
D.
hasUncertainOffspring
Indicates that an entity is associated with offspring whose existence, identity, or parentage is not fully certain or confirmed.
-
E.
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.
- 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_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:08 p.m.