Triple
T10185584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commentary on the Diatessaron |
E236899
|
entity |
| Predicate | canonicalScope |
P61710
|
FINISHED |
| Object | harmonized four Gospels |
—
|
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: harmonized four Gospels | Statement: [Commentary on the Diatessaron, canonicalScope, harmonized four Gospels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalScope Context triple: [Commentary on the Diatessaron, canonicalScope, harmonized four Gospels]
-
A.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
B.
scopeDefault
Indicates that something applies or is valid in the absence of a more specific or overriding scope.
-
C.
scopeOfReference
chosen
Indicates the range or domain of things, concepts, or entities to which a reference, statement, or expression applies.
-
D.
definesScopeFor
Indicates that one entity establishes or delimits the scope, boundaries, or applicability within which another entity operates or is interpreted.
-
E.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded36e9808190b385c5aec4889e00 |
completed | April 2, 2026, 4:14 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.