Triple
T35249821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammonites |
E1018065
|
entity |
| Predicate | ancestorAccordingToBible |
P5206
|
FINISHED |
| Object | Ben-Ammi |
—
|
NE NERFINISHED |
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: Ben-Ammi | Statement: [Ammonites, ancestorAccordingToBible, Ben-Ammi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestorAccordingToBible Context triple: [Ammonites, ancestorAccordingToBible, Ben-Ammi]
-
A.
ancestorMother
Indicates that one entity is a female ancestor (mother, grandmother, etc.) of another entity in a family lineage.
-
B.
theologicalRoot
Indicates that something originates from, is fundamentally based on, or is primarily explained by theological principles, doctrines, or beliefs.
-
C.
ancestor
chosen
Indicates that one entity is a forebear of another in a lineage, occurring in an earlier generation and connected through one or more parent-child relationships.
-
D.
ancestorHouse
Indicates that one entity is the house or dwelling associated with the ancestors of another entity.
-
E.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.