Triple
T313164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concerto Barocco |
E7648
|
entity |
| Predicate | laterCostumeStyle |
P8654
|
FINISHED |
| Object | white leotards and skirts |
—
|
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: white leotards and skirts | Statement: [Concerto Barocco, laterCostumeStyle, white leotards and skirts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCostumeStyle Context triple: [Concerto Barocco, laterCostumeStyle, white leotards and skirts]
-
A.
costumeType
Indicates the specific kind or category of costume associated with an entity.
-
B.
hasDressCode
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
C.
relatedStyle
chosen
Indicates that one style is associated with, similar to, or derived from another style in some relevant way.
-
D.
wears
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
-
E.
ceremonialDressFeature
Indicates that one entity is a characteristic, component, or distinguishing element of another entity’s ceremonial dress or attire.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4bd6a081909bdb57602c7093b4 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.