Triple
T34381809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Knock |
E882458
|
entity |
| Predicate | hasApparitionLocation |
P109658
|
FINISHED |
| Object | Knock, County Mayo, Ireland |
—
|
NE NERFINISHED |
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: Knock, County Mayo, Ireland | Statement: [Our Lady of Knock, hasApparitionLocation, Knock, County Mayo, Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApparitionLocation Context triple: [Our Lady of Knock, hasApparitionLocation, Knock, County Mayo, Ireland]
-
A.
hasHauntedLocation
Indicates that an entity possesses, is associated with, or includes a location that is believed to be haunted or supernaturally inhabited.
-
B.
reportedApparitionsVisibility
Indicates that an entity has reported seeing or being able to see apparitions.
-
C.
associatedWithApparition
chosen
Indicates a relationship where something is linked or connected to an apparition, such as being caused by, accompanying, or characterizing that apparition.
-
D.
isHauntedLocation
Indicates that a location is supernaturally affected or inhabited by ghosts, spirits, or other paranormal entities.
-
E.
apparitionFrequency
Indicates how often an entity appears, manifests, or becomes perceptible within a given context or timeframe.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 1, 2026, 1:59 a.m.