Triple
T3282682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Captain! My Captain! |
E68907
|
entity |
| Predicate | writtenInResponseTo |
P767
|
FINISHED |
| Object | death of Abraham Lincoln |
—
|
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: death of Abraham Lincoln | Statement: [O Captain! My Captain!, writtenInResponseTo, death of Abraham Lincoln]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenInResponseTo Context triple: [O Captain! My Captain!, writtenInResponseTo, death of Abraham Lincoln]
-
A.
wasResponseTo
chosen
Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
-
B.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
C.
commentedOnBy
Indicates that an entity has received a comment authored or posted by another entity.
-
D.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
E.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0345d448190a1f936abe7748e33 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.