Triple
T9458067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand pas de deux (Aurora and Désiré) |
E228067
|
entity |
| Predicate | centralQuality |
P89052
|
FINISHED |
| Object | lyricism |
—
|
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: lyricism | Statement: [Grand pas de deux (Aurora and Désiré), centralQuality, lyricism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralQuality Context triple: [Grand pas de deux (Aurora and Désiré), centralQuality, lyricism]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
C.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
centralBinaryComponent
Indicates that an entity functions as one of the primary stellar components in a central binary system.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f924f3081909dd937cbe6802881 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69ccbf9b080c819098934a18cf2bac5d |
completed | April 1, 2026, 6:47 a.m. |
Created at: March 30, 2026, 7:52 p.m.