Triple
T14690822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sycorax |
E345027
|
entity |
| Predicate | formerRulerOf |
P6674
|
FINISHED |
| Object | the island in The Tempest |
—
|
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: the island in The Tempest | Statement: [Sycorax, formerRulerOf, the island in The Tempest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRulerOf Context triple: [Sycorax, formerRulerOf, the island in The Tempest]
-
A.
lastMonarchOf
Indicates that one entity is the final reigning monarch of another entity, such as a country, kingdom, or territory.
-
B.
formerSovereign
chosen
Indicates that an entity once held sovereign (ruling) authority over another entity but no longer does.
-
C.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
D.
formerRulerState
Indicates that an entity previously held ruling authority over a given state or territory but no longer does so.
-
E.
predecessorAsDeFactoRuler
Indicates that one entity previously held actual ruling power over a domain or group, regardless of formal title, before another entity assumed that de facto control.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb585d46c81908d6964130914cec4 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.