Triple
T29959719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold Shoulder |
E761006
|
entity |
| Predicate | commonPatternPlacement |
P120669
|
FINISHED |
| Object | prints across bodice and sleeves including cut-out area |
—
|
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: prints across bodice and sleeves including cut-out area | Statement: [Cold Shoulder, commonPatternPlacement, prints across bodice and sleeves including cut-out area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonPatternPlacement Context triple: [Cold Shoulder, commonPatternPlacement, prints across bodice and sleeves including cut-out area]
-
A.
hasPatternPlacement
chosen
Indicates the spatial or positional arrangement of a pattern relative to or on another entity.
-
B.
typicalDecorationPlacement
Indicates the usual or most common spatial arrangement where a decoration is placed relative to another object or environment.
-
C.
airingPattern
Indicates the recurring schedule or pattern according to which something (such as a program or content) is broadcast or made available.
-
D.
typicalVariablePlacement
Indicates how variables are usually positioned or arranged within a given structure, expression, or context.
-
E.
commonArrangement
Indicates that the entities are typically organized, positioned, or configured together in a usual or standard way.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 29, 2026, 6:28 p.m.