Triple
T1478772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Royal |
E30902
|
entity |
| Predicate | grantedAtMonarchDiscretion |
P10140
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Princess Royal, grantedAtMonarchDiscretion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedAtMonarchDiscretion Context triple: [Princess Royal, grantedAtMonarchDiscretion, true]
-
A.
signedUnderMonarch
Indicates that a document or agreement was formally signed during the reign or authority of a specific monarch.
-
B.
canAdviseMonarchOn
Indicates that one entity has the authority or capacity to provide counsel or guidance to a monarch on matters of decision or policy.
-
C.
usedInMonarchy
Indicates that something is employed, practiced, or functions within the context of a monarchical system of government.
-
D.
providedMonarchTo
Indicates that one entity supplied or installed a monarch (such as a king or queen) to rule over another entity.
-
E.
awardedByDecreeOf
chosen
Indicates that something (such as a title, right, or benefit) is formally granted or conferred through an official decree or authoritative order.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6739d2481909ea8d8e075f62cf3 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.