Triple
T38399537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timahoe Round Tower |
E900856
|
entity |
| Predicate | doorwayDecoration |
P157812
|
FINISHED |
| Object | carved heads on capitals |
—
|
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: carved heads on capitals | Statement: [Timahoe Round Tower, doorwayDecoration, carved heads on capitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorwayDecoration Context triple: [Timahoe Round Tower, doorwayDecoration, carved heads on capitals]
-
A.
doorwayFeature
Indicates that one entity is a feature, characteristic, or structural element specifically associated with a doorway of another entity.
-
B.
hasEntranceDecoration
chosen
Indicates that an entity features a specific decorative element or arrangement at its entrance.
-
C.
decorationCategory
Indicates the classification or type of decoration that an item, element, or space belongs to.
-
D.
decoration
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
-
E.
decorations
Indicates that one entity adds, provides, or serves as ornamental or decorative elements for another entity.
- 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_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.