Triple
T23586126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite No. 2 for Tuba |
E582347
|
entity |
| Predicate | hasKeyFeatures |
P80525
|
FINISHED |
| Object | lyrical sections |
—
|
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: lyrical sections | Statement: [Suite No. 2 for Tuba, hasKeyFeatures, lyrical sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyFeatures Context triple: [Suite No. 2 for Tuba, hasKeyFeatures, lyrical sections]
-
A.
hasKeyFigure
Indicates that an entity includes, involves, or is characterized by an important or central person relevant to it.
-
B.
hasPrimaryFeature
chosen
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
C.
hasKeyPoint
Indicates that one entity includes, contains, or is associated with a specific key point or main idea represented by another entity.
-
D.
hasKeyAct
Indicates that one entity possesses or is associated with a primary or central action related to another entity.
-
E.
hasKeyAccord
Indicates that one entity possesses or defines the primary key or governing agreement that authorizes or controls another 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03030f88190bc325f7b4b0137f0 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:41 p.m.