Triple
T26895369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claudius |
E677883
|
entity |
| Predicate | admitsGuiltIn |
P4081
|
FINISHED |
| Object | soliloquy in Act 3, Scene 3 |
—
|
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: soliloquy in Act 3, Scene 3 | Statement: [Claudius, admitsGuiltIn, soliloquy in Act 3, Scene 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admitsGuiltIn Context triple: [Claudius, admitsGuiltIn, soliloquy in Act 3, Scene 3]
-
A.
pleadedGuilty
Indicates that a defendant formally admitted in court that they committed the offense with which they were charged.
-
B.
confessedTo
chosen
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another entity.
-
C.
acceptsConfession
Indicates that one entity receives and acknowledges a confession made by another entity.
-
D.
guiltyOf
Indicates that an entity has been judged or determined to have committed a particular offense, crime, or wrongful act.
-
E.
confesses
Indicates that one entity openly admits or acknowledges something, typically a wrongdoing, secret, or previously concealed fact, to another entity.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fa9a1ec8190bc4063656815a1c5 |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:47 a.m.