Triple
T14441730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agrippa II |
E358097
|
entity |
| Predicate | biblicalAppearance |
P3890
|
FINISHED |
| Object | Acts 25 |
—
|
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: Acts 25 | Statement: [Agrippa II, biblicalAppearance, Acts 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalAppearance Context triple: [Agrippa II, biblicalAppearance, Acts 25]
-
A.
associatedBiblicalFigure
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
-
B.
scripturalDescription
Indicates that one entity provides a description, account, or characterization of another as found in or based on scriptural or sacred texts.
-
C.
biblicalSourceCharacter
Indicates that one entity is the character or figure that serves as the source or origin for another entity within a biblical context.
-
D.
hasBiblicalConnection
chosen
Indicates a relationship in which one entity is connected to another through references, themes, origins, or influences derived from the Bible.
-
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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de915d28ec81909e72124e9dd67bfb |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.