Triple
T16127108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knock |
E391299
|
entity |
| Predicate | apparitionWitnessCount |
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, apparitionWitnessCount, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apparitionWitnessCount Context triple: [Knock, apparitionWitnessCount, 15]
-
A.
apparitionsRecognizedBy
Indicates that certain apparitions are acknowledged, identified, or accepted as genuine by a particular person, group, or authority.
-
B.
associatedWithApparition
Indicates a relationship where something is linked or connected to an apparition, such as being caused by, accompanying, or characterizing that apparition.
-
C.
reportedApparitionEntity
Indicates that an entity has been reported or described as an apparition in some account or observation.
-
D.
apparitionsDate
Indicates the date on which the apparitions are reported or believed to have occurred.
-
E.
apparitionsYear
Indicates the year in which the apparitions or appearances associated with an entity took place.
- F. None of above. chosen
Provenance (4 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20205bed48190a6930439738da191 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.