Triple
T13574722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacob |
E324251
|
entity |
| Predicate | positionInPatriarchs |
P110119
|
FINISHED |
| Object | third patriarch of the Israelites |
—
|
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: third patriarch of the Israelites | Statement: [Jacob, positionInPatriarchs, third patriarch of the Israelites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPatriarchs Context triple: [Jacob, positionInPatriarchs, third patriarch of the Israelites]
-
A.
rankAmongOrthodoxPatriarchs
Indicates the relative hierarchical position or order of an individual within the group of Orthodox patriarchs.
-
B.
patriarchRank
Indicates the hierarchical rank or level of authority held by a patriarch within a structured lineage or leadership system.
-
C.
currentPatriarch
Indicates that one entity is the present, officially recognized patriarch (religious or familial head) of another entity.
-
D.
enthronedAsPatriarch
Indicates that an individual has been formally installed or elevated to the office and authority of a patriarch.
-
E.
recognizesPatriarch
Indicates that one entity acknowledges or accepts another entity as a patriarchal authority or head.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02b1f108190a12af382d1de70bb |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf7fefa881908471f1400f813ccc |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:48 p.m.