Triple
T35865816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Her Majesty’s Canadian Ship |
E1037084
|
entity |
| Predicate | replacedWhenMonarchIs |
P183920
|
FINISHED |
| Object | king |
—
|
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: king | Statement: [Her Majesty’s Canadian Ship, replacedWhenMonarchIs, king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedWhenMonarchIs Context triple: [Her Majesty’s Canadian Ship, replacedWhenMonarchIs, king]
-
A.
monarchReplaced
Indicates that one monarch has been succeeded or replaced by another in a ruling position.
-
B.
usedWhenMonarchIs
chosen
Indicates that something is applied, valid, or occurs only under a specified condition or status of a monarch.
-
C.
monarchDuringForfeiture
Indicates the ruling monarch who was in power at the time a forfeiture (such as loss of title, land, or rights) occurred.
-
D.
reorganizedUnderMonarch
Indicates that an entity’s structure, governance, or organization was changed and placed under the authority or control of a monarch.
-
E.
monarchDeposed
Indicates that a monarch has been removed from power, typically against their will, by force, coercion, or formal deposition.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:06 p.m.