Triple
T28208698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamlet's love |
E717097
|
entity |
| Predicate | isDirectedFrom |
P49386
|
FINISHED |
| Object | Prince Hamlet |
—
|
NE NERFINISHED |
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: Prince Hamlet | Statement: [Hamlet's love, isDirectedFrom, Prince Hamlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDirectedFrom Context triple: [Hamlet's love, isDirectedFrom, Prince Hamlet]
-
A.
hasDirectionFrom
chosen
Indicates that one entity has a specific orientation or directional relationship when referenced from another entity.
-
B.
hasDirectedActor
Indicates that an entity has served as the director of another entity, such as a film, play, or production.
-
C.
flowsTo
Indicates that something moves or is directed from one location or entity toward and into another, typically in a continuous or channel-like manner.
-
D.
directed
Indicates that one entity served as the director or guiding authority responsible for overseeing and controlling the actions or production involving another entity.
-
E.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6430fdf488190b01ad19531e96991 |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:37 p.m.