Triple
T2283622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishmael |
E51334
|
entity |
| Predicate | familyLine |
P28764
|
FINISHED |
| Object | Abrahamic 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: Abrahamic lineage | Statement: [Ishmael, familyLine, Abrahamic lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyLine Context triple: [Ishmael, familyLine, Abrahamic lineage]
-
A.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
B.
familyOf
chosen
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
D.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
E.
familyVariant
Indicates a relationship where one entity is a variant or version within the same family or closely related group as 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc2445f388190af643878145f8249 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.