Triple
T38399531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timahoe Round Tower |
E900856
|
entity |
| Predicate | doorwayStyle |
P77408
|
FINISHED |
| Object | Romanesque arched doorway |
—
|
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 arched doorway | Statement: [Timahoe Round Tower, doorwayStyle, Romanesque arched doorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorwayStyle Context triple: [Timahoe Round Tower, doorwayStyle, Romanesque arched doorway]
-
A.
doorwayFeature
chosen
Indicates that one entity is a feature, characteristic, or structural element specifically associated with a doorway of another entity.
-
B.
doorType
Indicates the specific kind or category of door associated with an entity.
-
C.
gateStyle
Indicates the type or design style of a gate associated with an entity.
-
D.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
E.
hasDoorMaterial
Indicates that an entity’s door is made of, or primarily composed of, a specified material.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.