Triple
T31746976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosville |
E810296
|
entity |
| Predicate | hasFamilyLineageAssociation |
P124948
|
FINISHED |
| Object | Boswell family |
—
|
NE NERFINISHED |
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: Boswell family | Statement: [Bosville, hasFamilyLineageAssociation, Boswell family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyLineageAssociation Context triple: [Bosville, hasFamilyLineageAssociation, Boswell family]
-
A.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
B.
hasLineageMember
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
-
C.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
D.
lineageRelatedTo
chosen
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
E.
hasFamilyBranch
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 30, 2026, 11:27 p.m.