Triple
T27142211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knock Shrine |
E681843
|
entity |
| Predicate | numberOfWitnessesOfApparition |
P121573
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Knock Shrine, numberOfWitnessesOfApparition, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfWitnessesOfApparition Context triple: [Knock Shrine, numberOfWitnessesOfApparition, 15]
-
A.
apparitionWitnessCount
chosen
Indicates the number of distinct observers who witnessed a particular apparition event.
-
B.
apparitionsWitnessedBy
Indicates that one entity is an apparition or ghostly phenomenon that has been seen or experienced by another entity.
-
C.
apparitionsRecognizedBy
Indicates that certain apparitions are acknowledged, identified, or accepted as genuine by a particular person, group, or authority.
-
D.
numberOfWitnessesHeard
Indicates the count of witnesses whose testimony or statements were heard in a given event or proceeding.
-
E.
apparitionWitnessType
Indicates the specific manner or role in which an apparition is witnessed or experienced by an observer.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 27, 2026, 9:10 a.m.