Triple
T2641945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridgewater House, London |
E62887
|
entity |
| Predicate | redesignedInCentury |
P3336
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Bridgewater House, London, redesignedInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redesignedInCentury Context triple: [Bridgewater House, London, redesignedInCentury, 19th century]
-
A.
reorganizedInCentury
Indicates that an entity underwent a significant reorganization or structural change during the specified century.
-
B.
rebuiltInCentury
Indicates that an existing structure or entity was reconstructed or significantly rebuilt during a specified century.
-
C.
redesigned
chosen
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
-
D.
rediscoveredInCentury
Indicates that something previously known but lost or forgotten was found or recognized again during a specified century.
-
E.
constructionCentury
Indicates the century during which something was constructed or built.
- 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8fdc0bc8190b7fd102b87ee50d1 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.