Triple
T34381846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Knock |
E882458
|
entity |
| Predicate | apparitionCharacter |
P109658
|
FINISHED |
| Object | silent apparition |
—
|
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: silent apparition | Statement: [Our Lady of Knock, apparitionCharacter, silent apparition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apparitionCharacter Context triple: [Our Lady of Knock, apparitionCharacter, silent apparition]
-
A.
apparitionLittéraire
Indicates the event or relationship of a literary work or text coming into public existence, such as its first publication or debut in the literary sphere.
-
B.
associatedWithApparition
chosen
Indicates a relationship where something is linked or connected to an apparition, such as being caused by, accompanying, or characterizing that apparition.
-
C.
apparitionsRecognizedBy
Indicates that certain apparitions are acknowledged, identified, or accepted as genuine by a particular person, group, or authority.
-
D.
colorOfApparition
Indicates the specific color or hue that an apparition is perceived to have.
-
E.
hasGhostCharacter
Indicates that an entity includes, features, or is associated with a character that is a ghost.
- 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_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.