Triple
T27769632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pie Jesu |
E701704
|
entity |
| Predicate | isFrequentlyArrangedFor |
P80489
|
FINISHED |
| Object | solo voice and organ |
—
|
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: solo voice and organ | Statement: [Pie Jesu, isFrequentlyArrangedFor, solo voice and organ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyArrangedFor Context triple: [Pie Jesu, isFrequentlyArrangedFor, solo voice and organ]
-
A.
frequentlyArrangedFor
Indicates that one entity regularly organizes, schedules, or sets up something on behalf of another entity.
-
B.
commonlyArrangedFor
chosen
Indicates that one entity is typically organized, scheduled, or set up on behalf of another entity.
-
C.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
D.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
E.
isFrequentlyIncludedIn
Indicates that something is regularly or commonly contained or made part of something else.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 4:33 p.m.