Triple
T20011664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghost of King Hamlet |
E494603
|
entity |
| Predicate | sceneOfMajorAppearance |
P128577
|
FINISHED |
| Object | Act I, Scene V |
—
|
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: Act I, Scene V | Statement: [Ghost of King Hamlet, sceneOfMajorAppearance, Act I, Scene V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sceneOfMajorAppearance Context triple: [Ghost of King Hamlet, sceneOfMajorAppearance, Act I, Scene V]
-
A.
firstAppearanceScene
Indicates the scene in which an entity is shown or referenced for the first time within a work or sequence.
-
B.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
C.
scenes
Indicates that one entity is a scene or setting in which the other entity occurs, appears, or is depicted.
-
D.
notableSceneAssociation
chosen
Indicates an association between an entity and a notable or memorable scene in which it prominently appears or plays a significant role.
-
E.
placeOfMajorReception
Indicates the location where a person or entity received their primary or most significant formal reception, welcome, or honor.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623773d88190826616a02d3c3e69 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.