Triple
T9914783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Pavilion, Brighton |
E185839
|
entity |
| Predicate | significantRebuildingStart |
P72514
|
FINISHED |
| Object | 1815 |
—
|
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: 1815 | Statement: [Royal Pavilion, Brighton, significantRebuildingStart, 1815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantRebuildingStart Context triple: [Royal Pavilion, Brighton, significantRebuildingStart, 1815]
-
A.
largelyRebuilt
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
B.
majorRebuilder
Indicates that an entity plays a primary or leading role in reconstructing, restoring, or significantly rebuilding another entity.
-
C.
hasMajorReconstruction
chosen
Indicates that an entity has undergone a significant or extensive reconstruction or renovation.
-
D.
majorRebuildCompleted
Indicates that a significant reconstruction or overhaul of an entity has been fully completed.
-
E.
significantRestoration
Indicates that an entity has undergone a major or substantial restoration effort that notably improves or returns it to a previous condition.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb53ba1ac8190ba655133b81596d7 |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.