Triple
T30690203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rondo-Burleske: Allegro assai |
E781302
|
entity |
| Predicate | workKeyStatus |
P170032
|
FINISHED |
| Object | tonally complex and ambiguous |
—
|
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: tonally complex and ambiguous | Statement: [Rondo-Burleske: Allegro assai, workKeyStatus, tonally complex and ambiguous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workKeyStatus Context triple: [Rondo-Burleske: Allegro assai, workKeyStatus, tonally complex and ambiguous]
-
A.
worksStatus
Indicates the current state or condition of an entity’s work or project, such as whether it is planned, in progress, completed, or otherwise categorized.
-
B.
keyStatus
Indicates the current state or condition of a key (e.g., whether it is active, valid, revoked, or expired) in relation to its use or authorization.
-
C.
hasWorkStatus
Indicates the current employment or occupational state associated with an entity, such as whether it is active, inactive, or in a specific work condition.
-
D.
workIsKeySourceFor
Indicates that the referenced work serves as a primary or crucial source of information, evidence, or inspiration for the associated entity.
-
E.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b87acf881909bd5b32421ccf5c9 |
completed | May 2, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:33 p.m.