Triple
T17042860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To Whom It May Concern |
E413487
|
entity |
| Predicate | followedByPublicationDate |
P125622
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [To Whom It May Concern, followedByPublicationDate, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByPublicationDate Context triple: [To Whom It May Concern, followedByPublicationDate, 2005]
-
A.
followsInReleaseChronology
Indicates that one entity is released after another in a chronological sequence of releases.
-
B.
followedByReleaseYear
Indicates that one item is immediately succeeded by another item in terms of release year.
-
C.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
D.
followedByTitle
Indicates that one title directly succeeds another in a sequence or ordered list.
-
E.
subsequentPublication
Indicates that one publication was released after another in time, making it a later or follow-up work relative to the first.
- F. None of above. chosen
Provenance (4 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f870c0819087e4a20083d761f1 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.