Triple
T27415197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neva riverfront ensemble |
E692872
|
entity |
| Predicate | styleIncludes |
P52654
|
FINISHED |
| Object | Baroque 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: Baroque architecture | Statement: [Neva riverfront ensemble, styleIncludes, Baroque architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleIncludes Context triple: [Neva riverfront ensemble, styleIncludes, Baroque architecture]
-
A.
styleContribution
Indicates a relationship where one entity contributes to or influences the stylistic characteristics or aesthetic qualities of another.
-
B.
styleInFull
Indicates that something is presented, written, or expressed in its complete, unabbreviated, or fully detailed form.
-
C.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
D.
styleLanguage
Indicates a relationship where one entity specifies the language or linguistic style in which another entity is expressed, formatted, or presented.
-
E.
styleCategory
chosen
Indicates the stylistic classification or genre category that an item, work, or entity belongs to.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d19c9d88190938cdcd21112fc69 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:33 p.m.