Triple
T8229357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Composite order |
E192250
|
entity |
| Predicate | decorativeComplexity |
P80973
|
FINISHED |
| Object | highest among classical orders |
—
|
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: highest among classical orders | Statement: [Composite order, decorativeComplexity, highest among classical orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decorativeComplexity Context triple: [Composite order, decorativeComplexity, highest among classical orders]
-
A.
decorativeCategory
Indicates that one entity is classified as belonging to a particular decorative style, theme, or ornamentation category of another entity.
-
B.
ornamentalFeature
Indicates that one entity serves as a decorative or embellishing feature of another entity.
-
C.
decorativeFinish
Indicates that one entity serves as an ornamental or aesthetic surface treatment applied to another entity.
-
D.
decoration
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
-
E.
decorations
Indicates that one entity adds, provides, or serves as ornamental or decorative elements for 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7802417c81908837c31136c41a5c |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb3d6c34708190a987d68529cbb0b3 |
completed | March 31, 2026, 3:20 a.m. |
Created at: March 30, 2026, 5:46 p.m.