Triple
T1205821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 23 |
E25884
|
entity |
| Predicate | describesAbrahamAs |
P24623
|
FINISHED |
| Object | sojourner |
—
|
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: sojourner | Statement: [Genesis 23, describesAbrahamAs, sojourner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesAbrahamAs Context triple: [Genesis 23, describesAbrahamAs, sojourner]
-
A.
patriarch
Indicates a relationship where one entity serves as the male head or senior father-figure authority over a family, clan, or lineage of other entities.
-
B.
foundingAncestor
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
-
C.
divineFather
Indicates a paternal relationship in which one entity is regarded as the godly or divine father of another.
-
D.
patriarchFeatured
Indicates that a patriarch is prominently highlighted or given special emphasis in relation to something (such as a work, event, or context).
-
E.
regardsAsOnlyProphetAfterMoses
Indicates that one entity considers another entity to be the sole legitimate prophet following Moses.
- F. None of above. chosen
Provenance (4 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdc314c88190b1b5953834bfce7b |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:46 p.m.