Triple
T35004057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Settima Domenica di Pasqua |
E1009761
|
entity |
| Predicate | siCollocaTra |
P74300
|
FINISHED |
| Object | Ascensione |
—
|
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: Ascensione | Statement: [Settima Domenica di Pasqua, siCollocaTra, Ascensione]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siCollocaTra Context triple: [Settima Domenica di Pasqua, siCollocaTra, Ascensione]
-
A.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
B.
isIntermediateBetween
chosen
Indicates that one entity occupies a position or state that lies between two other entities in a sequence, range, or process.
-
C.
sungBetween
Indicates that something (typically a song or vocal passage) is performed vocally in a manner that connects or alternates between two entities or points in time.
-
D.
livesBetween
Indicates that one entity resides at a location that is spatially situated between two other reference entities or locations.
-
E.
currentBetween
Indicates that the current value of a quantity lies within a specified range between two boundary values.
- 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.