Triple
T37836749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four-source hypothesis |
E943357
|
entity |
| Predicate | includesSource |
P71759
|
FINISHED |
| Object | Gospel of Mark |
E9358
|
NE 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: Gospel of Mark | Statement: [Four-source hypothesis, includesSource, Gospel of Mark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSource Context triple: [Four-source hypothesis, includesSource, Gospel of Mark]
-
A.
sourcesInclude
chosen
Indicates that one entity’s content, data, or information is derived from, references, or incorporates material from another specified source.
-
B.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
C.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
-
D.
includesResources
Indicates that one entity contains, encompasses, or makes available specific resources as part of its composition or offering.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
- F. None of above.
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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cb41a4c81908dbbb8f8ed467c0a |
completed | June 28, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.