Triple
T33717832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teqoa |
E863924
|
entity |
| Predicate | hasBiblicalFigureAssociated |
P35021
|
FINISHED |
| Object | prophet Amos |
—
|
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: prophet Amos | Statement: [Teqoa, hasBiblicalFigureAssociated, prophet Amos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiblicalFigureAssociated Context triple: [Teqoa, hasBiblicalFigureAssociated, prophet Amos]
-
A.
associatedBiblicalFigure
chosen
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
-
B.
biblicalFigure
Indicates that an entity is recognized as a person mentioned or characterized within the Bible.
-
C.
hasReligiousFigureAssociation
Indicates a relationship in which an entity is connected or linked to a religious figure, such as through dedication, representation, influence, or affiliation.
-
D.
biblicalFigureFromClan
Indicates that a biblical figure belongs to, originates from, or is associated with a particular clan.
-
E.
biblicalFigureRole
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:44 a.m.