Triple
T19081213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miracle of the Sun |
E467035
|
entity |
| Predicate | hasPromisedDateClaim |
P58906
|
FINISHED |
| Object | apparition predicted for 13 October 1917 |
—
|
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: apparition predicted for 13 October 1917 | Statement: [Miracle of the Sun, hasPromisedDateClaim, apparition predicted for 13 October 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromisedDateClaim Context triple: [Miracle of the Sun, hasPromisedDateClaim, apparition predicted for 13 October 1917]
-
A.
hasPromDate
Indicates that one entity is the person who is accompanying another entity as their date to a prom event.
-
B.
hasAllegedDate
chosen
Indicates that an entity is associated with a date that is claimed or reported, but not confirmed as certain.
-
C.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
D.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
E.
hasAlternativeProposedDate
Indicates that an alternative date has been suggested or proposed in place of an original scheduled date.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e8f8148190942cca6dd3e30caf |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.