Triple
T27163641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Container Corporation of America |
E682725
|
entity |
| Predicate | usedDesignStyle |
P64230
|
FINISHED |
| Object | modernism |
—
|
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: modernism | Statement: [Container Corporation of America, usedDesignStyle, modernism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDesignStyle Context triple: [Container Corporation of America, usedDesignStyle, modernism]
-
A.
usedStyle
chosen
Indicates that one entity employed or applied a particular style, method, or manner associated with another entity.
-
B.
usedWithStyle
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
-
C.
usesAsStyleOf
Indicates that one entity adopts or applies another entity as a stylistic model, method, or manner of expression.
-
D.
productionDesignStyle
Indicates the visual and aesthetic approach used in designing the overall look and environment of a production.
-
E.
usesHouseStyle
Indicates that one entity follows or applies the specific house style (a defined set of stylistic or formatting conventions) associated with another entity.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:20 a.m.