Triple
T19136704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of Peter |
E468452
|
entity |
| Predicate | manuscriptDiscoveryDate |
P134573
|
FINISHED |
| Object | 1886–1887 |
—
|
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: 1886–1887 | Statement: [Gospel of Peter, manuscriptDiscoveryDate, 1886–1887]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manuscriptDiscoveryDate Context triple: [Gospel of Peter, manuscriptDiscoveryDate, 1886–1887]
-
A.
manuscriptDiscoveredBy
Indicates that a manuscript was found or brought to light through the efforts or actions of a particular agent or entity.
-
B.
manuscriptFoundIn
Indicates that a manuscript is discovered or located within a particular place, collection, or context.
-
C.
manuscriptCentury
Indicates the century during which a manuscript was created, copied, or primarily produced.
-
D.
earliestManuscripts
Indicates that the related entity (e.g., a text or work) is associated with its earliest known surviving manuscripts or documentary witnesses.
-
E.
latestManuscriptsDateTo
Indicates the most recent date up to which the manuscripts in question are known, valid, or considered.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3edd1c48190b86bef530ebbd092 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.