Triple
T34828212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remond |
E1003990
|
entity |
| Predicate | nameBearerFamilyRelation |
P181903
|
FINISHED |
| Object | son of Frederick Douglass |
—
|
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 of Frederick Douglass | Statement: [Remond, nameBearerFamilyRelation, son of Frederick Douglass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameBearerFamilyRelation Context triple: [Remond, nameBearerFamilyRelation, son of Frederick Douglass]
-
A.
familyNameRefersTo
Indicates that a specified family name designates or refers to a particular person, group, or lineage.
-
B.
nameBearerType
Indicates the specific role or capacity in which an entity bears or carries a given name (e.g., as a person, place, organization, or other type of name bearer).
-
C.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
-
D.
namesakeFamily
Indicates that one entity is a family or familial group that shares the same name as, or is named after, another entity.
-
E.
familyNameOfChildOf
Indicates that the subject is the family name (surname) borne by the child of the specified person or 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782f416c081908bdd9b1ad456f0e2 |
completed | May 3, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4 p.m.