Triple
T33439557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marian apparitions of 1877 |
E856322
|
entity |
| Predicate | hasRecognitionDate |
P23896
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [Marian apparitions of 1877, hasRecognitionDate, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecognitionDate Context triple: [Marian apparitions of 1877, hasRecognitionDate, 1977]
-
A.
recognitionDate
chosen
Indicates the date on which an entity, status, or achievement is formally acknowledged or officially recognized.
-
B.
unRecognitionDate
Indicates the date on which a previously recognized status, entity, or relationship is officially withdrawn or no longer acknowledged.
-
C.
hasReceivedRecognitionFor
Indicates that an entity has been acknowledged, honored, or formally recognized for a particular achievement, contribution, or quality.
-
D.
legacyRecognizedAt
Indicates that an entity’s lasting impact, contributions, or heritage are formally acknowledged at a particular time, place, or context.
-
E.
hasLaterRecognition
Indicates that one entity receives acknowledgment, fame, or formal recognition at a time later than another entity or later than an initial reference point.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:37 a.m.