Triple
T35004074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Settima Domenica di Pasqua |
E1009761
|
entity |
| Predicate | èOsservataIn |
P34153
|
FINISHED |
| Object | Rito romano |
—
|
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: Rito romano | Statement: [Settima Domenica di Pasqua, èOsservataIn, Rito romano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: èOsservataIn Context triple: [Settima Domenica di Pasqua, èOsservataIn, Rito romano]
-
A.
isCommonlyFoundAt
Indicates that an entity typically or frequently occurs, appears, or is present in a particular location or context.
-
B.
isEspeciallyObservedIn
Indicates that something is most notably or frequently observed within a particular context, condition, or group compared to others.
-
C.
inhabitedIn
Indicates that an entity lives, resides, or has its dwelling within a specified place or location.
-
D.
mainlyObservedIn
Indicates that something occurs, appears, or is found predominantly within a particular context, location, group, or condition.
-
E.
isObservedIn
chosen
Indicates that something (such as a phenomenon, property, or behavior) is detected, recorded, or found to occur within a particular context, setting, or environment.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.