Triple
T28963015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mebarak family |
E731960
|
entity |
| Predicate | hasMaternalConnectionTo |
P153341
|
FINISHED |
| Object | Shakira’s children |
—
|
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: Shakira’s children | Statement: [Mebarak family, hasMaternalConnectionTo, Shakira’s children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaternalConnectionTo Context triple: [Mebarak family, hasMaternalConnectionTo, Shakira’s children]
-
A.
hasMatrilinealConnection
Indicates a relationship where one entity is connected to another through a line of descent traced exclusively through female ancestors.
-
B.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
C.
maternalConnectionTo
chosen
Indicates a relationship in which one entity is the mother of, or has a motherly bond or role toward, another entity.
-
D.
maternalAncestorOf
Indicates that one entity is an ancestor of another specifically through a chain of maternal (mother-to-child) relationships.
-
E.
maternalCousinOf
Indicates that one person is the cousin of another through their mother’s side of the family.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: April 28, 2026, 8:50 a.m.