Triple
T6330143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendelssohn's Elijah |
E141956
|
entity |
| Predicate | keyMovementsKnownFor |
P70889
|
FINISHED |
| Object | large-scale choruses |
—
|
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: large-scale choruses | Statement: [Mendelssohn's Elijah, keyMovementsKnownFor, large-scale choruses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyMovementsKnownFor Context triple: [Mendelssohn's Elijah, keyMovementsKnownFor, large-scale choruses]
-
A.
movementAlsoKnownAs
Indicates that a movement is referred to by an alternative name or alias.
-
B.
laterKnownFor
Indicates that an entity became recognized or notable for something at a later time than the context or event currently being referred to.
-
C.
underlyingKnownFor
Indicates that one entity is fundamentally or primarily recognized as the basis or main reason for another entity’s notability or fame.
-
D.
alsoKnownFor
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
-
E.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
- F. None of above. chosen
Provenance (4 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651334c08190a9514faa36e7812d |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c064c080148190a7c3218867f1f572 |
completed | March 22, 2026, 9:53 p.m. |
Created at: March 22, 2026, 4:30 p.m.