Triple
T34865595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VI Sunday of Easter |
E1004998
|
entity |
| Predicate | hasTypicalMassProper |
P199545
|
FINISHED |
| Object | readings for the Sixth Sunday of Easter |
—
|
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: readings for the Sixth Sunday of Easter | Statement: [VI Sunday of Easter, hasTypicalMassProper, readings for the Sixth Sunday of Easter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalMassProper Context triple: [VI Sunday of Easter, hasTypicalMassProper, readings for the Sixth Sunday of Easter]
-
A.
typicalMassRange
Indicates the usual or expected range of mass values associated with an entity.
-
B.
hasTypeOfMass
Indicates that one entity possesses or is characterized by a particular kind or category of mass.
-
C.
hasMassScale
Indicates that an entity is associated with a particular mass measurement scale or system used to quantify its mass.
-
D.
hasMasses
Indicates that one entity possesses or is associated with one or more masses (quantities of matter).
-
E.
holdsRegularMasses
Indicates that an entity routinely conducts or hosts religious mass services on a regular schedule.
- F. None of above. chosen
Provenance (4 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
| PDg | Predicate description generation | batch_69ff4163a8548190b0eaafd0a377b141 |
completed | May 9, 2026, 2:14 p.m. |
Created at: May 3, 2026, 4 p.m.