Triple
T37922757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor |
E946007
|
entity |
| Predicate | appliedToMovementCount |
P32659
|
FINISHED |
| Object | three-movement concerto |
—
|
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: three-movement concerto | Statement: [Emperor, appliedToMovementCount, three-movement concerto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToMovementCount Context triple: [Emperor, appliedToMovementCount, three-movement concerto]
-
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.
movementCountDescription
Indicates the textual description or explanation associated with a specific count or number of movements.
-
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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 3, 2026, 4:20 p.m.