Triple
T21027541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alba Trueba |
E517977
|
entity |
| Predicate | relationshipWithGrandfather |
P142527
|
FINISHED |
| Object | conflicted |
—
|
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: conflicted | Statement: [Alba Trueba, relationshipWithGrandfather, conflicted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithGrandfather Context triple: [Alba Trueba, relationshipWithGrandfather, conflicted]
-
A.
relationshipToGrandparents
Indicates the familial relationship that an entity has with their grandparents, such as biological, step, or adoptive connections.
-
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.
grandfatherOfSon
Indicates that one person is the grandfather of another person’s son.
-
D.
paternalGrandchildOf
Indicates that one entity is the grandchild of another through the latter’s son (i.e., via the paternal line).
-
E.
grandfatherIs
Indicates that one entity is the grandfather (parent of a parent) of another entity.
- F. None of above. chosen
Provenance (4 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7d93908190a2c29a4051fb5acc |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:55 p.m.