Triple
T7595967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Profundis |
E179857
|
entity |
| Predicate | endDateWritten |
P19743
|
FINISHED |
| Object | March 1897 |
—
|
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: March 1897 | Statement: [De Profundis, endDateWritten, March 1897]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endDateWritten Context triple: [De Profundis, endDateWritten, March 1897]
-
A.
hasDateWritten
chosen
Indicates that something is associated with the specific date on which it was written.
-
B.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
endDateOfficialUse
Indicates the date on which the official use or validity of something (such as a document, status, or authorization) comes to an end.
-
D.
laterWrittenIn
Indicates that one text or version was written at a later time than another, establishing a chronological order between the writings.
-
E.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d39e9481908bec42447c97e3f8 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.