Triple
T31303924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukedom of Cambridge |
E798281
|
entity |
| Predicate | monarchWhoCanGrant |
P87922
|
FINISHED |
| Object | British sovereign |
—
|
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: British sovereign | Statement: [Dukedom of Cambridge, monarchWhoCanGrant, British sovereign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchWhoCanGrant Context triple: [Dukedom of Cambridge, monarchWhoCanGrant, British sovereign]
-
A.
monarchWhoGrants
chosen
Indicates a relationship where a monarch bestows, confers, or grants something (such as rights, titles, lands, or privileges) to another party.
-
B.
monarchicalPowerExercisedBy
Indicates that monarchical authority or ruling power is exercised or carried out by a specified agent or entity.
-
C.
confersPowerOnMonarch
Indicates that one entity grants or bestows governing authority or ruling power upon a monarch.
-
D.
monarchIs
Indicates that one entity serves as the ruling monarch (such as king, queen, or equivalent sovereign) of another entity, typically a state or territory.
-
E.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 9:14 p.m.