Triple
T16558208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamech |
E402263
|
entity |
| Predicate | belongsToGenealogy |
P4276
|
FINISHED |
| Object | Sethite genealogy |
—
|
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: Sethite genealogy | Statement: [Lamech, belongsToGenealogy, Sethite genealogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToGenealogy Context triple: [Lamech, belongsToGenealogy, Sethite genealogy]
-
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.
belongsToFamily
chosen
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
C.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
D.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
E.
hasGenealogicalInterest
Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576bce0c819087ab36f7dec5c394 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.