Triple
T157769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Septuagint |
E3214
|
entity |
| Predicate | hasCanonicalStatus |
P3927
|
FINISHED |
| Object | Old Testament canon in Eastern Orthodoxy |
—
|
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: Old Testament canon in Eastern Orthodoxy | Statement: [Septuagint, hasCanonicalStatus, Old Testament canon in Eastern Orthodoxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalStatus Context triple: [Septuagint, hasCanonicalStatus, Old Testament canon in Eastern Orthodoxy]
-
A.
canonicalStatus
chosen
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
B.
hasAuthorityStatus
Indicates that one entity holds a particular level or type of official power, control, or decision-making authority over another entity or within a defined context.
-
C.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
D.
hasIconicStatus
Indicates that an entity holds a widely recognized, emblematic, or culturally significant status within a particular domain or context.
-
E.
isCanonicalZone
Indicates that a given zone is the primary, standard, or officially recognized version among possible alternatives.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25830136881909f5ecb2cb22097b2 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a2565f30848190a2a71fdb7dc140b5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.