Triple
T28294120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brown-Tubbs family |
E713510
|
entity |
| Predicate | hasBlendedFamilyStructure |
P92492
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Brown-Tubbs family, hasBlendedFamilyStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlendedFamilyStructure Context triple: [Brown-Tubbs family, hasBlendedFamilyStructure, true]
-
A.
hasFamilySituation
chosen
Indicates the familial status or circumstances that apply to an entity, such as their family composition, responsibilities, or living situation.
-
B.
hasTwoMothers
Indicates that an entity is related to or cared for by two distinct mother figures.
-
C.
hasFamilyOrganization
Indicates that an entity is associated with, belongs to, or is structured within a particular family-based organizational unit or system.
-
D.
hasFamilyBranch
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
-
E.
hasNumberOfChildrenWithSpouse
Indicates the count of children that an individual has specifically with a given spouse.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6448643f48190b5d292584036de6e |
completed | May 2, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:31 p.m.