Triple
T5386763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Church Slavonic Bible |
E120219
|
entity |
| Predicate | earliestIn |
P10938
|
FINISHED |
| Object | Slavic Bible translations |
—
|
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: Slavic Bible translations | Statement: [Old Church Slavonic Bible, earliestIn, Slavic Bible translations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestIn Context triple: [Old Church Slavonic Bible, earliestIn, Slavic Bible translations]
-
A.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
B.
earliestStage
Indicates that one entity represents the first or minimum stage, phase, or step in a defined ordered sequence relative to another.
-
C.
earliestState
chosen
Indicates that one state or condition occurs before all other related states in time, representing the earliest point in a sequence.
-
D.
isOldestOrderOf
Indicates that one order is the earliest or first created among a set of related orders for a given context or entity.
-
E.
isOldest
Indicates that one entity has a greater age than all other relevant entities in the comparison set.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f6f39c8190aa6af12370e3d12b |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.