Triple
T26046335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raio Palace |
E647841
|
entity |
| Predicate | hasOrnamentationType |
P19073
|
FINISHED |
| Object | Rococo decorative elements |
—
|
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: Rococo decorative elements | Statement: [Raio Palace, hasOrnamentationType, Rococo decorative elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrnamentationType Context triple: [Raio Palace, hasOrnamentationType, Rococo decorative elements]
-
A.
hasOrnamentation
chosen
Indicates that an entity possesses decorative features or embellishments applied to its surface or structure.
-
B.
allowsOrnamentation
Indicates that one entity permits or enables decorative additions or embellishments to be applied to another entity.
-
C.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
D.
hasOrchestralFeature
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
-
E.
hasArticulationType
Indicates the specific manner or type of connection or joint by which two parts or entities are linked or articulated.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 22, 2026, 9:10 a.m.