Triple
T36732151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sayings Gospel Q |
E907369
|
entity |
| Predicate | proposedDateRange |
P9416
|
FINISHED |
| Object | c. 40–70 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: c. 40–70 CE | Statement: [Sayings Gospel Q, proposedDateRange, c. 40–70 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedDateRange Context triple: [Sayings Gospel Q, proposedDateRange, c. 40–70 CE]
-
A.
typicalEndDateRange
Indicates the usual or expected range of end dates associated with an event, activity, or time-bounded entity.
-
B.
timePeriodProposed
chosen
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
C.
recommendedDate
Indicates the date on which something is advised or suggested to occur, be used, or be acted upon.
-
D.
representsDateRange
Indicates that a subject is associated with, valid for, or applicable during a specific start-to-end date range.
-
E.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.