Triple
T16585953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mousetrap (play-within-a-play) |
E402956
|
entity |
| Predicate | parallelsEvent |
P6686
|
FINISHED |
| Object | King Hamlet’s murder |
—
|
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: King Hamlet’s murder | Statement: [The Mousetrap (play-within-a-play), parallelsEvent, King Hamlet’s murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelsEvent Context triple: [The Mousetrap (play-within-a-play), parallelsEvent, King Hamlet’s murder]
-
A.
parallelEvent
Indicates that two or more events occur at the same time or overlap in time without a required order between them.
-
B.
parallels
Indicates that one entity runs alongside or corresponds to another in a way that maintains a consistent separation or similarity without intersecting.
-
C.
parentEvent
Indicates that one event serves as the higher-level or originating event from which another event is derived, contained, or logically dependent.
-
D.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
E.
portraysEvent
chosen
Indicates that one entity depicts, represents, or illustrates a particular event.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599cbc448190bc80eef4ad58eb41 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.