Triple
T21397783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex tremendae |
E527831
|
entity |
| Predicate | commonlyPerformedWith |
P9966
|
FINISHED |
| Object | complete Mozart Requiem |
—
|
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: complete Mozart Requiem | Statement: [Rex tremendae, commonlyPerformedWith, complete Mozart Requiem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyPerformedWith Context triple: [Rex tremendae, commonlyPerformedWith, complete Mozart Requiem]
-
A.
commonlyPerformedAs
Indicates that an action, behavior, or role is typically or frequently carried out in a particular manner, form, or context.
-
B.
commonlyPerformedIn
Indicates that an action or activity is typically or frequently carried out within a particular context, location, or setting.
-
C.
oftenPerformedOn
Indicates that an action or process is frequently carried out on, or applied to, a particular entity.
-
D.
performedWith
chosen
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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.