Triple
T3815989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifth Sunday of Lent |
E84254
|
entity |
| Predicate | hasApproximateDateRange |
P46071
|
FINISHED |
| Object | mid‑March to mid‑April |
—
|
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‑March to mid‑April | Statement: [Fifth Sunday of Lent, hasApproximateDateRange, mid‑March to mid‑April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDateRange Context triple: [Fifth Sunday of Lent, hasApproximateDateRange, mid‑March to mid‑April]
-
A.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
representsDateRange
chosen
Indicates that a subject is associated with, valid for, or applicable during a specific start-to-end date range.
-
C.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
D.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
E.
historicalRange
Indicates the time period over which something existed, was active, or was relevant in history.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.