Triple
T36315139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monasterboice |
E894168
|
entity |
| Predicate | roundTowerFunction |
P49901
|
FINISHED |
| Object | bell 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: bell tower | Statement: [Monasterboice, roundTowerFunction, bell tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundTowerFunction Context triple: [Monasterboice, roundTowerFunction, bell tower]
-
A.
towerFunction
chosen
Indicates that one entity serves as a tower-like structure or performs the function of a tower in relation to another entity.
-
B.
roundTowerStoreys
Indicates that one entity is a specific number of storeys associated with, or contained in, a round tower.
-
C.
timeballTowerFunction
Indicates that something serves the function or role of a time ball tower, typically used to signal standardized time visually.
-
D.
waterTowerFunction
Indicates that an entity serves the role or function of a water tower, typically storing and supplying water within a system or area.
-
E.
castleFunction
Indicates the primary role, purpose, or use that a castle serves (e.g., defense, residence, administration, or symbolism).
- 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.