Triple
T31570557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 |
E805546
|
entity |
| Predicate | hasMovementCountRange |
P32659
|
FINISHED |
| Object | 3–5 |
—
|
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: 3–5 | Statement: [Symphony No. 3, hasMovementCountRange, 3–5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovementCountRange Context triple: [Symphony No. 3, hasMovementCountRange, 3–5]
-
A.
numberOfMovements
chosen
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
B.
hasMovementLegacy
Indicates that an entity carries forward, preserves, or significantly influences the ongoing impact, traditions, or ideals of a particular movement.
-
C.
hasMovementVariant
Indicates that one movement is an alternative or variant form of another movement.
-
D.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
E.
hasMovementOrder
Indicates that one entity is assigned or associated with a specific directive or sequence for movement or relocation.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 30, 2026, 10:19 p.m.