Triple
T6750872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letters to a Young Poet |
E154337
|
entity |
| Predicate | lettersWrittenBetween |
P73290
|
FINISHED |
| Object | 1902 |
—
|
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: 1902 | Statement: [Letters to a Young Poet, lettersWrittenBetween, 1902]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lettersWrittenBetween Context triple: [Letters to a Young Poet, lettersWrittenBetween, 1902]
-
A.
writesLettersTo
Indicates that one entity composes and sends letters directed to another entity.
-
B.
correspondedWith
Indicates that two entities engaged in mutual communication, typically by exchanging messages or letters over a period of time.
-
C.
letterer
Indicates that one entity serves as the letterer of another, typically responsible for drawing or designing the lettering (such as text or captions) in that work.
-
D.
letter3
Indicates that one entity is the third letter (or character) of another entity, typically a string or word.
-
E.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
- 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d3264b7481908816a4d19543fb7b |
completed | March 27, 2026, 6:57 p.m. |
Created at: March 27, 2026, 2:11 p.m.