Triple
T3120316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Bezae |
E65167
|
entity |
| Predicate | containsCanonicalSection |
P37078
|
FINISHED |
| Object | 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: four Gospels | Statement: [Codex Bezae, containsCanonicalSection, four Gospels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCanonicalSection Context triple: [Codex Bezae, containsCanonicalSection, four Gospels]
-
A.
hasSectionIn
chosen
Indicates that one entity contains or includes another entity as a section or subdivision within it.
-
B.
hasSectionOn
Indicates that one entity (typically a document or resource) contains a dedicated section or part that specifically addresses or discusses another entity or topic.
-
C.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
D.
hasSect
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
-
E.
hasCanalSection
Indicates a relationship where one entity includes, contains, or is associated with a specific section or segment of a canal.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4eb6a6081909df41f67999eb4ff |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.