Triple
T35891029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Berkeley |
E1037781
|
entity |
| Predicate | governingMonarchJurisdiction |
P20995
|
FINISHED |
| Object | English Crown |
E8113
|
NE 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: English Crown | Statement: [Viscount Berkeley, governingMonarchJurisdiction, English Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingMonarchJurisdiction Context triple: [Viscount Berkeley, governingMonarchJurisdiction, English Crown]
-
A.
governingMonarchs
Indicates that the subject is the monarch who holds ruling authority over the object (such as a country, territory, or people).
-
B.
governingMonarch
chosen
Indicates that one entity serves as the reigning monarch who holds sovereign authority over the other entity.
-
C.
reignOfMonarch
Indicates the period during which a specific monarch holds ruling authority over a realm or territory.
-
D.
governingMonarchAtTime
Indicates that a specified person is the reigning monarch of a given polity during a particular time or time interval.
-
E.
legalStatusOfMonarch
Indicates the legal status or standing that a monarch holds within a given legal or constitutional framework.
- F. None of above.
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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a021706e21c81909b83e2b4d9c4130c |
completed | May 11, 2026, 5:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ae2382408190a486e995f103be43 |
completed | June 22, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_6a0216861214819097d2177755bc19d7 |
completed | May 11, 2026, 5:48 p.m. |
Created at: May 3, 2026, 4:06 p.m.