Triple
T8156787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polonius |
E190469
|
entity |
| Predicate | spiesOn |
P28505
|
FINISHED |
| Object | Laertes |
E190470
|
NE 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: Laertes | Statement: [Polonius, spiesOn, Laertes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Laertes Context triple: [Polonius, spiesOn, Laertes]
-
A.
Laertes
Laertes is a figure in Greek mythology best known as the aging king of Ithaca and the father of the hero Odysseus in Homer's Odyssey.
-
B.
Laertes
chosen
Laertes is a character in William Shakespeare's tragedy "Hamlet," known as Polonius's son who seeks revenge against Prince Hamlet for his father's death.
-
C.
Rosencrantz
Rosencrantz is a minor courtier and former schoolmate of Prince Hamlet who, along with Guildenstern, is used by King Claudius to spy on Hamlet in Shakespeare’s tragedy "Hamlet."
-
D.
Fortinbras
Fortinbras is a Norwegian prince in Shakespeare's "Hamlet" who serves as a foil to Hamlet and ultimately claims the Danish throne.
-
E.
Mercutio
Mercutio is a witty, charismatic nobleman and close companion of Romeo in Shakespeare’s tragedy "Romeo and Juliet," known for his sharp tongue and tragic fate.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7266bc148190984060b7b95effb5 |
completed | March 31, 2026, 7:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd3471def08190a221e92fc4a2e9d7 |
completed | April 1, 2026, 3:06 p.m. |
Created at: March 30, 2026, 5:37 p.m.