Triple
T29180883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dante Symphony |
E739740
|
entity |
| Predicate | ParadisoMovementStatus |
P16365
|
FINISHED |
| Object | not composed as full 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: not composed as full movement | Statement: [Dante Symphony, ParadisoMovementStatus, not composed as full movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ParadisoMovementStatus Context triple: [Dante Symphony, ParadisoMovementStatus, not composed as full movement]
-
A.
movementStatus
chosen
Indicates the current state or condition of an entity’s movement, such as whether and how it is moving or stationary.
-
B.
positionInMovement
Indicates the specific role or placement an entity holds within a broader movement or collective action.
-
C.
isMovement
Indicates that the subject undergoes or performs a change in position or location over time.
-
D.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
E.
movementDetermines
Indicates that one entity’s movement or motion pattern determines, controls, or decisively influences the movement or state of 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663450ba88190aaa465977605d426 |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:57 a.m.