Triple
T6340160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of Mark |
E142603
|
entity |
| Predicate | textualIssue |
P70073
|
FINISHED |
| Object | longer ending of Mark |
—
|
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: longer ending of Mark | Statement: [Gospel of Mark, textualIssue, longer ending of Mark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualIssue Context triple: [Gospel of Mark, textualIssue, longer ending of Mark]
-
A.
textualTransmission
Indicates the transfer or communication of information through written or printed text from one source to another.
-
B.
textType
Indicates the classification of a text according to its type, format, or genre.
-
C.
textBy
Indicates that a given text or written content was authored or produced by a particular entity.
-
D.
textuallySystematizedBy
Indicates that information, concepts, or data are organized, structured, or codified into a systematic textual form by a particular agent or source.
-
E.
textualStructure
Indicates how parts of a text are organized and related to each other within its overall structure.
- F. None of above. chosen
Provenance (4 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0674311388190bb069a07a7ff60ef |
completed | March 22, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:30 p.m.