Triple
T37775275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humour |
E941664
|
entity |
| Predicate | textUsedInMovement |
P189537
|
FINISHED |
| Object | one of the movements of Symphony No. 13 "Babi Yar" |
—
|
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 movements of Symphony No. 13 "Babi Yar" | Statement: [Humour, textUsedInMovement, one of the movements of Symphony No. 13 "Babi Yar"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textUsedInMovement Context triple: [Humour, textUsedInMovement, one of the movements of Symphony No. 13 "Babi Yar"]
-
A.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
B.
namedForMovement
Indicates that one entity is named after or in honor of a particular movement, such as a social, political, artistic, or ideological movement.
-
C.
usesMove
Indicates that an entity performs or executes a specific move or action.
-
D.
isMovement
Indicates that the subject undergoes or performs a change in position or location over time.
-
E.
isMovementOf
Indicates that one entity represents the motion, relocation, or change of position of another entity.
- F. None of above. chosen
Provenance (4 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.