Triple
T10139141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slavic Orthodox Churches |
E226934
|
entity |
| Predicate | sharesCanonicalText |
P45461
|
FINISHED |
| Object | Septuagint-based Old Testament |
—
|
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: Septuagint-based Old Testament | Statement: [Slavic Orthodox Churches, sharesCanonicalText, Septuagint-based Old Testament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCanonicalText Context triple: [Slavic Orthodox Churches, sharesCanonicalText, Septuagint-based Old Testament]
-
A.
canonicalText
chosen
Indicates that a standardized, authoritative textual representation is associated with an entity or expression.
-
B.
canonicalTextSection
Indicates that one text section is the authoritative or standard version associated with another representation or variant of that section.
-
C.
textContent
Indicates that one entity is the textual content or written material contained within another entity.
-
D.
notableText
Indicates that a particular piece of text is especially significant, prominent, or worthy of attention in relation to the associated entity or context.
-
E.
textuallySystematizedBy
Indicates that information, concepts, or data are organized, structured, or codified into a systematic textual form by a particular agent or source.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cde8851844819092330e74561b7e34 |
completed | April 2, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:06 p.m.