Triple
T33439557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marian apparitions of 1877 |
E856322
|
entity |
| Predicate | hasRecognitionDate |
—
|
GENERATED |
| Object | 1977 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 1, 2026, 1:37 a.m.