Triple
T31200416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aghaboe |
E795456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic ecclesiastical site |
C60123
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic ecclesiastical site Context triple: [Aghaboe, instanceOf, historic ecclesiastical site]
-
A.
religious-historical location
chosen
A religious-historical location is a place that holds both spiritual significance and historical importance due to its association with religious events, figures, or traditions over time.
-
B.
historic monument
A historic monument is a significant structure, site, or object preserved for its cultural, architectural, or historical importance, symbolizing and commemorating events, people, or eras of the past.
-
C.
Historic church
A historic church is a long-standing religious building of significant architectural, cultural, and spiritual importance that reflects the beliefs, artistry, and community life of its era.
-
D.
historical religious institution
A historical religious institution is an organized body or establishment that has played a significant role in shaping and preserving religious beliefs, practices, and cultural traditions over an extended period in history.
-
E.
religious site
A religious site is a designated place or structure where individuals or communities engage in worship, rituals, and other practices associated with their faith or spiritual beliefs.
- F. None of above.
Provenance (1 batch)
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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:09 p.m.