Triple
T17967641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Disappointment |
E449254
|
entity |
| Predicate | expectedEventDate |
P77362
|
FINISHED |
| Object | 1844-10-22 |
—
|
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: 1844-10-22 | Statement: [Great Disappointment, expectedEventDate, 1844-10-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedEventDate Context triple: [Great Disappointment, expectedEventDate, 1844-10-22]
-
A.
recommendedDate
Indicates the date on which something is advised or suggested to occur, be used, or be acted upon.
-
B.
estimatedStartDate
chosen
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
C.
namedForEventDate
Indicates that something is named after or in reference to the date on which a particular event occurred.
-
D.
subsequentArrivalDate
Indicates that one entity’s arrival date occurs after the arrival date of another related entity.
-
E.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b13935908190b5269a84a3df2460 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.