Triple
T9117680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joy to the World |
E218762
|
entity |
| Predicate | widelyRecordedBy |
P82412
|
FINISHED |
| Object | various choirs |
—
|
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: various choirs | Statement: [Joy to the World, widelyRecordedBy, various choirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyRecordedBy Context triple: [Joy to the World, widelyRecordedBy, various choirs]
-
A.
mostFamouslyRecordedBy
Indicates that an item (such as a work, song, or performance) is best known or most widely associated with having been recorded by a particular entity.
-
B.
frequentlyRecordedBy
Indicates that an entity is often documented, captured, or logged by a particular agent, system, or recording process.
-
C.
mainlyRecordedBy
Indicates that the primary or most significant recording of something (such as a work, event, or data set) was made by a particular agent or entity.
-
D.
isOftenRecordedWith
Indicates that one entity is frequently documented, captured, or logged at the same time as another entity.
-
E.
alsoRecordedBy
chosen
Indicates that the same work, event, or material has been additionally recorded by another recorder or recording entity.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a5e2ac8190b602ef0c77deb2fa |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.