Triple
T17592421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Han |
E428478
|
entity |
| Predicate | typicalFamilyStructure |
P39277
|
FINISHED |
| Object | patrilineal lineage |
—
|
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: patrilineal lineage | Statement: [Han, typicalFamilyStructure, patrilineal lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFamilyStructure Context triple: [Han, typicalFamilyStructure, patrilineal lineage]
-
A.
familyType
chosen
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
B.
hasFamilySituation
Indicates the familial status or circumstances that apply to an entity, such as their family composition, responsibilities, or living situation.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
E.
familySize
Indicates the number of individuals that belong to a given family unit.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e79dac8190953a1ce8fc015b20 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.