Triple
T38177378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Gough |
E1000251
|
entity |
| Predicate | hasOriginalCreationMonarch |
P84555
|
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 Gough, hasOriginalCreationMonarch, British monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalCreationMonarch Context triple: [Baron Gough, hasOriginalCreationMonarch, British monarch]
-
A.
monarchCreatedBy
Indicates that a monarch came into existence, was established, or was formally instituted through the action or decision of a specific creator or authority.
-
B.
originalMonarch
Indicates that a monarch is the first or founding ruler of a particular realm, title, or dynasty.
-
C.
monarchOnCreation
chosen
Indicates that an individual became the reigning monarch at the moment of a political entity’s creation or establishment.
-
D.
hasMonarchFrom
Indicates that a political entity is ruled by, or has as its monarch, a specific individual from a given time or context.
-
E.
previousCreationMonarch
Indicates that one monarch directly preceded another in holding a particular created title or office.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:29 p.m.