Triple
T21397948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Offertorium: Hostias |
E527835
|
entity |
| Predicate | movementNumberWithinOffertory |
P12040
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Offertorium: Hostias, movementNumberWithinOffertory, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementNumberWithinOffertory Context triple: [Offertorium: Hostias, movementNumberWithinOffertory, 2]
-
A.
movementNumber
chosen
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
B.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
C.
movementNumberInOp130
Indicates the specific movement number of a work within Opus 130.
-
D.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
E.
hasOffering
Indicates that one entity provides, presents, or makes available an offering (such as a product, service, or item) to another entity or context.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b16a9c7c819083bd2d298106fdf1 |
completed | April 22, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:14 p.m.