Triple
T5109869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamlet |
E115188
|
entity |
| Predicate | character |
P662
|
FINISHED |
| Object | Horatio |
E48874
|
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: Horatio | Statement: [Hamlet, character, Horatio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horatio Context triple: [Hamlet, character, Horatio]
-
A.
Horatio
chosen
Horatio is a variant form of the given name Horace, historically associated with Latin origins and classical literature.
-
B.
Romeo
Romeo is a small statutory town located in Conejos County in southern Colorado, United States.
-
C.
Arthur
Arthur is a masculine given name of Celtic origin, historically associated with legendary and royal figures, most famously King Arthur of Britain.
-
D.
Arthur
Arthur is the codename of the refined, high-ranking leader of the Kingsman organization in the action-spy film "Kingsman: The Secret Service."
-
E.
Arthur
Arthur is a long-running animated children's television series that follows the everyday adventures and life lessons of Arthur Read, an anthropomorphic aardvark, and his friends and family.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ac19e88190aa8cc8b930a58d2d |
completed | March 20, 2026, 4:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bebaa322d08190911dd2ca91405c3c |
completed | March 21, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:41 p.m.