Triple
T24177015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gebirah |
E599308
|
entity |
| Predicate | hasBiblicalFunction |
P128865
|
FINISHED |
| Object | intercessor before the king |
—
|
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: intercessor before the king | Statement: [Gebirah, hasBiblicalFunction, intercessor before the king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiblicalFunction Context triple: [Gebirah, hasBiblicalFunction, intercessor before the king]
-
A.
biblicalFunction
chosen
Indicates that one entity serves a particular role, duty, or purpose in a biblical or scriptural context in relation to another entity.
-
B.
hasBiblicalConnection
Indicates a relationship in which one entity is connected to another through references, themes, origins, or influences derived from the Bible.
-
C.
scripturalFunction
Indicates the role or purpose that a text or passage serves within a scriptural or religious context.
-
D.
functionInBiblicalPeriod
Indicates that an entity held or performed a particular role, office, or function during a specified biblical historical period.
-
E.
hasScripturalRole
Indicates that an entity holds a specific role, function, or position within a scriptural or religious text.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.