Triple
T35098364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John |
E1012932
|
entity |
| Predicate | scriptureLanguageForm |
P137319
|
FINISHED |
| Object | Yochanan |
—
|
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: Yochanan | Statement: [John, scriptureLanguageForm, Yochanan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptureLanguageForm Context triple: [John, scriptureLanguageForm, Yochanan]
-
A.
scripturalLanguageName
Indicates the name of the language in which a given scripture or sacred text is written.
-
B.
biblicalFormOf
chosen
Indicates that one term is the traditional or canonical form used in the Bible for a name or expression corresponding to another term.
-
C.
scriptureLanguageRegister
Indicates the specific linguistic register or style in which a piece of scripture is expressed (e.g., formal, liturgical, vernacular).
-
D.
hasLanguageOfScripture
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
-
E.
scripturalLanguageContext
Indicates the linguistic or textual context in which a scriptural passage, term, or reference is expressed or interpreted.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:01 p.m.