Triple
T8676422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parade |
E205925
|
entity |
| Predicate | balletsRussesProduction |
P84424
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Parade, balletsRussesProduction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balletsRussesProduction Context triple: [Parade, balletsRussesProduction, true]
-
A.
balletCompany
Indicates that one entity is a ballet company associated with, representing, or responsible for another entity (such as a performance, dancer, or production).
-
B.
balletInActs
Indicates that a ballet is structured or divided into a specified number of acts.
-
C.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
D.
balletCompanyAssociation
Indicates an affiliation or formal relationship between an entity and a ballet company, such as membership, employment, or representation.
-
E.
choreographedIn
Indicates that an entity (typically a choreographer or group) created or arranged the choreography for a performance, work, or event in a specified context or production.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc4ae517108190a71a86349815f4ce |
completed | March 31, 2026, 10:29 p.m. |
Created at: March 30, 2026, 6:32 p.m.