Triple
T404931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synodal Bible |
E9362
|
entity |
| Predicate | basedOnLanguageStage |
P11161
|
FINISHED |
| Object | modern Russian |
—
|
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: modern Russian | Statement: [Synodal Bible, basedOnLanguageStage, modern Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnLanguageStage Context triple: [Synodal Bible, basedOnLanguageStage, modern Russian]
-
A.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
B.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
C.
isScheduledLanguageOf
Indicates that a particular language is officially planned or designated to be used for a specific event, program, or context.
-
D.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
E.
draftedInLanguage
Indicates that a document, text, or content was originally written or composed using a specific natural language.
- F. None of above. chosen
Provenance (4 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca37fe881909802126952dfdd59 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.