Triple
T3386775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calton Hill |
E71319
|
entity |
| Predicate | hasMonumentStyle |
P39583
|
FINISHED |
| Object | Greek Revival architecture (National Monument) |
—
|
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: Greek Revival architecture (National Monument) | Statement: [Calton Hill, hasMonumentStyle, Greek Revival architecture (National Monument)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonumentStyle Context triple: [Calton Hill, hasMonumentStyle, Greek Revival architecture (National Monument)]
-
A.
monumentStyle
chosen
Indicates the architectural or artistic style characterizing a monument in relation to that monument.
-
B.
hasCathedralStyle
Indicates that something possesses or is characterized by a particular architectural style associated with a cathedral.
-
C.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
D.
monumentState
Indicates that a monument is located within, or officially associated with, a particular state or state-level administrative region.
-
E.
hasGravestoneStyle
Indicates that an entity’s gravestone is characterized by or associated with a particular style or design.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb66448fc8190a8582145f02bb1d9 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.