Triple
T15375966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turtle clan (Lenape) |
E367668
|
entity |
| Predicate | kinshipLine |
P36142
|
FINISHED |
| Object | maternal line |
—
|
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: maternal line | Statement: [Turtle clan (Lenape), kinshipLine, maternal line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kinshipLine Context triple: [Turtle clan (Lenape), kinshipLine, maternal line]
-
A.
kinshipNetwork
Indicates a familial relationship structure connecting individuals through blood, marriage, or adoption within a broader family network.
-
B.
genealogicalLine
chosen
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
C.
sharesFamilyLineageWith
Indicates that two entities descend from the same family line or share common ancestors.
-
D.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
E.
ancestralLinks
Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5ece1081908d7c1289258b9c1f |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:18 a.m.