Triple
T29010274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valse noble |
E736543
|
entity |
| Predicate | movementNumberInCarnaval |
P154281
|
FINISHED |
| Object | one of the middle movements |
—
|
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: one of the middle movements | Statement: [Valse noble, movementNumberInCarnaval, one of the middle movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementNumberInCarnaval Context triple: [Valse noble, movementNumberInCarnaval, one of the middle movements]
-
A.
carnivalFrequency
Indicates how often a carnival event occurs within a given time period.
-
B.
numberOfDances
Indicates the quantity or count of dances associated with a given entity or event.
-
C.
carnivalRecognizedAs
Indicates that one carnival is acknowledged, designated, or officially regarded as a particular type, status, or identity.
-
D.
typicalNumberOfDancers
Indicates the usual or standard number of dancers involved in a particular dance, performance, or context.
-
E.
movementCountDescription
chosen
Indicates the textual description or explanation associated with a specific count or number of movements.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 9:41 a.m.