Triple
T21888921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen in Council |
E540484
|
entity |
| Predicate | appliesToMonarchTitle |
P117093
|
FINISHED |
| Object | Queen Regnant |
—
|
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: Queen Regnant | Statement: [Queen in Council, appliesToMonarchTitle, Queen Regnant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToMonarchTitle Context triple: [Queen in Council, appliesToMonarchTitle, Queen Regnant]
-
A.
appliedToMonarch
Indicates that an action, policy, or attribute is directed toward or exercised upon a monarch.
-
B.
servedMonarchTitle
Indicates that one entity held a specific royal or noble title while serving as the reigning monarch over another entity.
-
C.
hasMonarchTitleSince
Indicates that an entity has held a specific monarch title continuously starting from a given point in time.
-
D.
styleOfMonarchTitle
Indicates the specific formal style or wording used in the official title of a monarch.
-
E.
typeOfMonarchyTitle
chosen
Indicates that a given title is a specific type or category of monarchy-related title (e.g., king, queen, emperor) within a monarchical system.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ef2b648190bbd78f6b3958d2ee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.