Triple
T6442660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corpus Christi |
E138261
|
entity |
| Predicate | isTransferredToSundayIn |
P9580
|
FINISHED |
| Object | many episcopal conferences |
—
|
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: many episcopal conferences | Statement: [Corpus Christi, isTransferredToSundayIn, many episcopal conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTransferredToSundayIn Context triple: [Corpus Christi, isTransferredToSundayIn, many episcopal conferences]
-
A.
ifOnSundayObservedOn
Indicates that when an event or obligation falls on a Sunday, it is instead observed or carried out on a different specified day.
-
B.
observedIfOnSunday
chosen
Indicates that the observation or event occurs or is recorded only when the relevant time falls on a Sunday.
-
C.
sundayLawDate
Indicates the date on which a specific Sunday law is enacted, comes into effect, or is scheduled to be observed.
-
D.
designatedDayFor
Indicates that a specific day is officially assigned or reserved for a particular purpose, event, or activity.
-
E.
trackingWeekEnd
Indicates the point in time marking when a specified tracking period or tracking week concludes.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698b030481908b7bb4e16a8b3339 |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.