Triple
T31142873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Upper Ossory |
E793836
|
entity |
| Predicate | governingMonarchType |
P21959
|
FINISHED |
| Object | British monarch |
—
|
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 monarch | Statement: [Baron Upper Ossory, governingMonarchType, British monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingMonarchType Context triple: [Baron Upper Ossory, governingMonarchType, British monarch]
-
A.
governingMonarch
Indicates that one entity serves as the reigning monarch who holds sovereign authority over the other entity.
-
B.
monarchType
chosen
Indicates the specific kind or category of monarchy or monarch associated with an entity.
-
C.
representedMonarch
Indicates that one entity formally acted on behalf of, or served as the official representative of, a monarch in some capacity or context.
-
D.
governingMonarchs
Indicates that the subject is the monarch who holds ruling authority over the object (such as a country, territory, or people).
-
E.
governingMonarchAtTime
Indicates that a specified person is the reigning monarch of a given polity during a particular time or time interval.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: April 29, 2026, 9:06 p.m.