Triple
T34157284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Denmark in Hamlet |
E876172
|
entity |
| Predicate | borderThreat |
P43422
|
FINISHED |
| Object | Norwegian forces under Fortinbras |
—
|
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: Norwegian forces under Fortinbras | Statement: [Kingdom of Denmark in Hamlet, borderThreat, Norwegian forces under Fortinbras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderThreat Context triple: [Kingdom of Denmark in Hamlet, borderThreat, Norwegian forces under Fortinbras]
-
A.
borderMonitored
Indicates that a border between two regions or entities is actively being watched, controlled, or surveilled.
-
B.
borderGuardDuty
Indicates that an entity is assigned to perform security or monitoring duties at a border or checkpoint.
-
C.
facesThreat
chosen
Indicates that an entity is exposed to or confronted by a potential danger, risk, or harmful situation.
-
D.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
E.
targetsThreat
Indicates that one entity is directing an action or focus specifically toward a perceived threat.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: May 1, 2026, 1:54 a.m.