Triple
T36912332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Pearl (for Variation 25) |
E912942
|
entity |
| Predicate | appliedToMovementNumber |
P12040
|
FINISHED |
| Object | 25 |
—
|
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: 25 | Statement: [Black Pearl (for Variation 25), appliedToMovementNumber, 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToMovementNumber Context triple: [Black Pearl (for Variation 25), appliedToMovementNumber, 25]
-
A.
precededByMovementNumber
Indicates that one movement occurs immediately before another movement in an ordered sequence.
-
B.
numberOfMovements
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
C.
movementNumber
chosen
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
D.
haveMovementFor
Indicates that an entity exhibits or is assigned a specific type or pattern of movement in relation to another entity or context.
-
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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: May 3, 2026, 4:13 p.m.