Triple
T1062656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge of Sighs, Cambridge |
E22940
|
entity |
| Predicate | hasDecorativeElements |
P19073
|
FINISHED |
| Object | tracery windows |
—
|
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: tracery windows | Statement: [Bridge of Sighs, Cambridge, hasDecorativeElements, tracery windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecorativeElements Context triple: [Bridge of Sighs, Cambridge, hasDecorativeElements, tracery windows]
-
A.
hasIconicElement
Indicates that something contains or features a distinctive, widely recognized element that symbolizes its identity or significance.
-
B.
hasOrnamentation
chosen
Indicates that an entity possesses decorative features or embellishments applied to its surface or structure.
-
C.
isWearableDecoration
Indicates that one entity serves as a decorative item intended to be worn on the body by another entity.
-
D.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
E.
hasIconicStructure
Indicates that an entity possesses a structure or feature that is widely recognized as emblematic or symbolically representative of it.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f68a54819084326d87c3498252 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.