Triple
T4857227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brechin Cathedral |
E108565
|
entity |
| Predicate | hasDoorwayStyle |
P8655
|
FINISHED |
| Object | Romanesque sculptured doorway on round tower |
—
|
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: Romanesque sculptured doorway on round tower | Statement: [Brechin Cathedral, hasDoorwayStyle, Romanesque sculptured doorway on round tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoorwayStyle Context triple: [Brechin Cathedral, hasDoorwayStyle, Romanesque sculptured doorway on round tower]
-
A.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
B.
hasStageDoor
Indicates that a venue or building possesses a dedicated stage door used for performers and staff to access backstage areas.
-
C.
hasEndDoors
Indicates that an object or structure is equipped with doors located at one or more of its ends.
-
D.
doorType
chosen
Indicates the specific kind or category of door associated with an entity.
-
E.
hasBlackFrontDoor
Indicates that one entity possesses or features a front door whose color is black.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.