Triple
T9036858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | world premiere of Dvořák Symphony No. 9 "From the New World" |
E216516
|
entity |
| Predicate | movementCountOfWork |
P32659
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [world premiere of Dvořák Symphony No. 9 "From the New World", movementCountOfWork, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementCountOfWork Context triple: [world premiere of Dvořák Symphony No. 9 "From the New World", movementCountOfWork, 4]
-
A.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
B.
numberOfMovements
chosen
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
C.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
D.
workMovement
Indicates a relationship where an entity’s work or employment involves changing physical locations, such as traveling or relocating as part of their job.
-
E.
numberOfWorks
Indicates the total count of works associated with a given 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6ac1f08c8190be0e37115df11f31 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.