Triple
T16254153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kedesh |
E394585
|
entity |
| Predicate | biblicalGeographyRole |
P85021
|
FINISHED |
| Object | northern city of refuge in Galilee |
—
|
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: northern city of refuge in Galilee | Statement: [Kedesh, biblicalGeographyRole, northern city of refuge in Galilee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalGeographyRole Context triple: [Kedesh, biblicalGeographyRole, northern city of refuge in Galilee]
-
A.
regionInScripturalContext
Indicates that a geographic region is referenced or holds significance within a particular scriptural or religious text context.
-
B.
biblicalFigureRole
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
C.
geographicRole
chosen
Indicates a relationship where one entity serves a specific geographic function, status, or role in relation to another location or area.
-
D.
biblicalCityName
Indicates that the entity is identified by a name used for a city in the Bible.
-
E.
associatedBiblicalFigure
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24598c9488190a92df7d8b1824724 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.