Triple
T19257639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sledge sisters |
E481555
|
entity |
| Predicate | sharesParentage |
P112367
|
FINISHED |
| Object | Sledge family |
—
|
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: Sledge family | Statement: [Sledge sisters, sharesParentage, Sledge family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesParentage Context triple: [Sledge sisters, sharesParentage, Sledge family]
-
A.
sharesParentsWith
chosen
Indicates that two entities have the same parents, making them siblings or otherwise sharing identical parentage.
-
B.
spouseParentage
Indicates that one entity is a parent of the other entity’s spouse.
-
C.
sharesChildrenWith
Indicates that two entities are co-parents, having one or more children in common.
-
D.
parentageInSomeSources
Indicates that a parental relationship between entities is reported or asserted in some, but not necessarily all, available sources.
-
E.
parentageIncludes
Indicates that a given parentage or lineage set contains or encompasses a particular parent or ancestral relationship.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb862f848190977987e0327ce41d |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.