Triple
T20377070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collegio del Cambio |
E497719
|
entity |
| Predicate | interiorCharacterizedBy |
P101261
|
FINISHED |
| Object | rich polychrome decoration |
—
|
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: rich polychrome decoration | Statement: [Collegio del Cambio, interiorCharacterizedBy, rich polychrome decoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interiorCharacterizedBy Context triple: [Collegio del Cambio, interiorCharacterizedBy, rich polychrome decoration]
-
A.
interiorStyle
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
B.
typicalInterior
Indicates that one entity is the usual or characteristic interior of another entity.
-
C.
interiorDecoratedBy
Indicates that the interior of a space or structure has been designed or decorated by a specific agent or entity.
-
D.
partOfInteriorDesign
Indicates that one entity is a component or element within the interior design scheme of another entity.
-
E.
hasRichInteriorDecoration
chosen
Indicates that an entity features elaborate, ornate, or luxuriously detailed interior decoration.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678ad74348190ac57d38eaa56beb3 |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.