Triple
T29180882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dante Symphony |
E739740
|
entity |
| Predicate | originalPlanIncluded |
P199928
|
FINISHED |
| Object | Paradiso movement |
—
|
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: Paradiso movement | Statement: [Dante Symphony, originalPlanIncluded, Paradiso movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPlanIncluded Context triple: [Dante Symphony, originalPlanIncluded, Paradiso movement]
-
A.
originalPlan
Indicates that one entity is the initial or primary plan or intended course of action associated with another entity.
-
B.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
C.
hasBasePlan
Indicates that an entity is associated with or derived from a specified foundational or default plan.
-
D.
initiallySupportsPlan
Indicates that an entity expresses support for a plan at the beginning of a process, period, or scenario.
-
E.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: April 28, 2026, 11:57 a.m.