Triple
T33991236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal County of Berkshire |
E871547
|
entity |
| Predicate | ceremonialStatusGrantedByMonarch |
P55784
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Royal County of Berkshire, ceremonialStatusGrantedByMonarch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialStatusGrantedByMonarch Context triple: [Royal County of Berkshire, ceremonialStatusGrantedByMonarch, yes]
-
A.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
-
B.
ceremonialStatus
chosen
Indicates the formal or symbolic standing an entity holds within a ritual, tradition, or official ceremony.
-
C.
dateGrantedTitleRoyal
Indicates the specific date on which a royal title was formally granted to an entity.
-
D.
royalWarrantGrantedIn
Indicates that an official royal warrant or authorization was granted in a specified place or jurisdiction.
-
E.
royalTitleConfirmed
Indicates that an individual's royal title has been formally validated or officially recognized.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f703c848208190acbf540d488972f7 |
completed | May 3, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69f70101ba1c819099380274e6df9a4d |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.