Triple
T31335111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keith Anderson |
E799149
|
entity |
| Predicate | relationshipToMainFamily |
P201537
|
FINISHED |
| Object | son-in-law of Florida and James Evans |
—
|
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: son-in-law of Florida and James Evans | Statement: [Keith Anderson, relationshipToMainFamily, son-in-law of Florida and James Evans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToMainFamily Context triple: [Keith Anderson, relationshipToMainFamily, son-in-law of Florida and James Evans]
-
A.
relationshipToMain
chosen
Indicates that an entity has a specified type of relationship or association to a primary or main entity.
-
B.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
-
C.
subjectFamilyRelation
Indicates that there is a familial relationship of some kind between the subject entity and another entity.
-
D.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
E.
relationshipToParent
Indicates the specific familial or social role an entity has in relation to its parent entity.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:16 p.m.