Triple
T4239805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Reading Room rotunda |
E94782
|
entity |
| Predicate | hasInteriorDecorationStyle |
P5509
|
FINISHED |
| Object | richly ornamented |
—
|
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: richly ornamented | Statement: [Main Reading Room rotunda, hasInteriorDecorationStyle, richly ornamented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorDecorationStyle Context triple: [Main Reading Room rotunda, hasInteriorDecorationStyle, richly ornamented]
-
A.
interiorStyle
chosen
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
B.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
C.
usesHouseStyle
Indicates that one entity follows or applies the specific house style (a defined set of stylistic or formatting conventions) associated with another entity.
-
D.
hasCeilingDecoration
Indicates that an entity features or is adorned with a decorative element on its ceiling.
-
E.
decoration
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e77fb5c8190b298818acb68ff63 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.