Triple
T36987442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candy Ride |
E915001
|
entity |
| Predicate | isGrandsireOf |
P61441
|
FINISHED |
| Object | Epicenter |
—
|
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: Epicenter | Statement: [Candy Ride, isGrandsireOf, Epicenter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGrandsireOf Context triple: [Candy Ride, isGrandsireOf, Epicenter]
-
A.
forefatherOf
Indicates that one person is an ancestor, typically from an earlier generation, of another person.
-
B.
possibleGrandfatherOf
Indicates that one individual may be the grandfather of another, typically as the father of one of the other person’s parents, but with some uncertainty or lack of confirmation.
-
C.
grandfatherIs
chosen
Indicates that one entity is the grandfather (parent of a parent) of another entity.
-
D.
paternalGreatGrandparentOf
Indicates that one person is the father of another person’s grandparent, making him that person’s paternal great-grandparent.
-
E.
paternalGrandchildOf
Indicates that one entity is the grandchild of another through the latter’s son (i.e., via the paternal line).
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.