Triple
T28546554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahoghill |
E722454
|
entity |
| Predicate | hasChristianHeritage |
P88447
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ahoghill, hasChristianHeritage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChristianHeritage Context triple: [Ahoghill, hasChristianHeritage, true]
-
A.
hasAncientChristianHeritage
chosen
Indicates that an entity possesses a historical connection to early or longstanding Christian traditions, communities, or influences.
-
B.
hasLiturgicalHeritage
Indicates that one entity possesses or is associated with the liturgical tradition, practices, or rites originating from another entity.
-
C.
followsReformationHeritageOf
Indicates that one entity continues, aligns with, or is influenced by the theological, ecclesial, or cultural traditions originating from the Protestant Reformation as embodied in another entity.
-
D.
inChristianizedTradition
Indicates that something is understood, practiced, or represented within the context of Christianized religious or cultural tradition.
-
E.
hasChristianCommunity
Indicates that a place or entity possesses or hosts an established Christian community.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 28, 2026, 3:39 a.m.