Triple
T2436439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Epistle to Timothy |
E52971
|
entity |
| Predicate | approximateDateTraditional |
P31438
|
FINISHED |
| Object | mid-60s CE |
—
|
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: mid-60s CE | Statement: [Second Epistle to Timothy, approximateDateTraditional, mid-60s CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateTraditional Context triple: [Second Epistle to Timothy, approximateDateTraditional, mid-60s CE]
-
A.
traditionallyDated
chosen
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
B.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
D.
dateSecularized
Indicates the date on which a religious or ecclesiastical entity was formally converted to secular (non-religious) status.
-
E.
typicalDates
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.