Triple
T31838688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadow of Hamlet |
E812740
|
entity |
| Predicate | usesAsFramework |
P9089
|
FINISHED |
| Object | 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: Hamlet | Statement: [Shadow of Hamlet, usesAsFramework, Hamlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAsFramework Context triple: [Shadow of Hamlet, usesAsFramework, Hamlet]
-
A.
isPartOfFramework
Indicates that one entity functions as a component, module, or element within a larger structured framework or system.
-
B.
appliesFramework
chosen
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
-
C.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
-
D.
usesFrame
Indicates that one entity employs, relies on, or is structured around a particular frame, framework, or reference structure provided by another entity.
-
E.
parentFramework
Indicates that one framework serves as the higher-level or containing framework from which another framework is derived, organized, or structured.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 30, 2026, 11:48 p.m.