Triple
T24026900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urban IV |
E594987
|
entity |
| Predicate | feastInstituted |
P103315
|
FINISHED |
| Object | Feast of Corpus Christi |
—
|
NE NERFINISHED |
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: Feast of Corpus Christi | Statement: [Urban IV, feastInstituted, Feast of Corpus Christi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feastInstituted Context triple: [Urban IV, feastInstituted, Feast of Corpus Christi]
-
A.
institutedFeast
Indicates that an authority or group formally established and put into practice a particular feast or festival as an ongoing observance.
-
B.
feastEstablishedBy
chosen
Indicates that a particular feast or celebratory event was created, instituted, or formally initiated by a specific agent or authority.
-
C.
feastEstablished
Indicates that a feast or celebratory event has been formally instituted or set up, typically as an ongoing or recognized occasion.
-
D.
feastSignificance
Indicates the cultural, religious, or social importance attributed to a particular feast or celebratory meal.
-
E.
feastOf
Indicates that one entity is the religious or ceremonial feast day associated with another entity (such as a person, event, or deity).
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76c083c819090784ecb42effbae |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:54 p.m.