Triple
T31873565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaux-Arts Institute of Design |
E813674
|
entity |
| Predicate | styleEmphasized |
P65476
|
FINISHED |
| Object | Beaux-Arts architecture |
—
|
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: Beaux-Arts architecture | Statement: [Beaux-Arts Institute of Design, styleEmphasized, Beaux-Arts architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleEmphasized Context triple: [Beaux-Arts Institute of Design, styleEmphasized, Beaux-Arts architecture]
-
A.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
C.
accentStyle
Indicates the manner or pattern in which an entity’s accent or emphasis is applied or presented.
-
D.
designEmphasizes
chosen
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
E.
accentColor
Indicates the color used as a highlight or emphasis within a visual design or interface.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 11:55 p.m.