Triple
T2257227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaudete Sunday |
E49754
|
entity |
| Predicate | occursBetween |
P15632
|
FINISHED |
| Object | December 11 and December 17 |
—
|
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: December 11 and December 17 | Statement: [Gaudete Sunday, occursBetween, December 11 and December 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursBetween Context triple: [Gaudete Sunday, occursBetween, December 11 and December 17]
-
A.
appliesBetween
Indicates that a specified condition, rule, or relationship holds specifically between two or more entities, rather than for each entity individually.
-
B.
runsBetween
chosen
Indicates a relationship where something extends, operates, or connects from one point, entity, or state to another along a path or interval.
-
C.
concludedBetween
Indicates that an agreement, arrangement, or formal relationship has been finalized between two or more parties.
-
D.
occursAt
Indicates that an event or action takes place at a specific time or location.
-
E.
usedBetween
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1570dc88190bb2b17ed4c25dbb5 |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.