Triple
T11416910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | monster of Glamis |
E270514
|
entity |
| Predicate | rumoredIdentity |
P99192
|
FINISHED |
| Object | heir to the Earl of Strathmore |
—
|
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: heir to the Earl of Strathmore | Statement: [monster of Glamis, rumoredIdentity, heir to the Earl of Strathmore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rumoredIdentity Context triple: [monster of Glamis, rumoredIdentity, heir to the Earl of Strathmore]
-
A.
disputedIdentities
Indicates that there is disagreement or conflict over how the identities of the involved entities are defined, classified, or recognized.
-
B.
knowsSecretIdentityOf
Indicates that one entity is aware of the hidden or private true identity of another entity.
-
C.
identityRevealedIn
Indicates that an entity’s true identity becomes known or disclosed within a specified context, source, or situation.
-
D.
rumoredTarget
Indicates that an entity is believed or speculated, based on rumor or unconfirmed information, to be the intended target of another entity or action.
-
E.
hasSecretIdentity
Indicates that an entity possesses an alternate, hidden identity that is not publicly known.
- F. None of above. chosen
Provenance (4 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b0236c81908122ce3fc7b4fde7 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.