Triple
T30445265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulcinella Variations |
E774560
|
entity |
| Predicate | scoreTitle |
P169770
|
FINISHED |
| Object | Pulcinella |
—
|
NE NERFINISHED |
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: Pulcinella | Statement: [Pulcinella Variations, scoreTitle, Pulcinella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreTitle Context triple: [Pulcinella Variations, scoreTitle, Pulcinella]
-
A.
scoresWhen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or event.
-
B.
scores
Indicates that one entity achieves or is assigned a numerical result, rating, or points in relation to another entity, such as a test, game, or evaluation.
-
C.
titleGameScore
Indicates the score or result achieved in a specific game or match associated with a title or competition.
-
D.
scoreStyle
Indicates the manner or method in which a score (such as a rating, grade, or numerical result) is expressed or formatted in the relationship.
-
E.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686be108c8190a8ec98dc286ab03b |
completed | May 2, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:08 p.m.