Triple
T20011540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosencrantz |
E494600
|
entity |
| Predicate | receivesDocument |
P95780
|
FINISHED |
| Object | letter ordering Hamlet’s death |
—
|
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: letter ordering Hamlet’s death | Statement: [Rosencrantz, receivesDocument, letter ordering Hamlet’s death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesDocument Context triple: [Rosencrantz, receivesDocument, letter ordering Hamlet’s death]
-
A.
receivedDocument
chosen
Indicates that one entity has been given and taken possession of a document from another entity or source.
-
B.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
C.
issuedDocumentOn
Indicates that an entity formally produced or released a document on a specific date or occasion.
-
D.
documentsResponseTo
Indicates that one entity records, describes, or formally captures the reply, outcome, or reaction to another entity.
-
E.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623773d88190826616a02d3c3e69 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.