Triple
T24981733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | En-dor |
E625185
|
entity |
| Predicate | hasBiblicalFigureVisitor |
P137076
|
FINISHED |
| Object | Saul |
—
|
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: Saul | Statement: [En-dor, hasBiblicalFigureVisitor, Saul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiblicalFigureVisitor Context triple: [En-dor, hasBiblicalFigureVisitor, Saul]
-
A.
hasOldTestamentFigurePresent
chosen
Indicates that an Old Testament figure is present or involved in the given context or situation.
-
B.
associatedBiblicalFigure
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
-
C.
hasBiblicalConnection
Indicates a relationship in which one entity is connected to another through references, themes, origins, or influences derived from the Bible.
-
D.
biblicalFigureFromClan
Indicates that a biblical figure belongs to, originates from, or is associated with a particular clan.
-
E.
hasReligiousFigureAssociation
Indicates a relationship in which an entity is connected or linked to a religious figure, such as through dedication, representation, influence, or affiliation.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490636f88190b8e614202f6d7a65 |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:02 a.m.