Triple
T3847996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fid. Def. |
E85219
|
entity |
| Predicate | usedInMonarchStyle |
P15439
|
FINISHED |
| Object | royal titulary of British monarchs |
—
|
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: royal titulary of British monarchs | Statement: [Fid. Def., usedInMonarchStyle, royal titulary of British monarchs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMonarchStyle Context triple: [Fid. Def., usedInMonarchStyle, royal titulary of British monarchs]
-
A.
usedInMonarchy
Indicates that something is employed, practiced, or functions within the context of a monarchical system of government.
-
B.
royalStyle
chosen
Indicates the formal manner or title by which a monarch or royal person is officially addressed or referred to.
-
C.
monarchUsedAsResidence
Indicates that a monarch uses or has used a particular place as their residence.
-
D.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
E.
associatedWithMonarch
Indicates a relationship where an entity has a connection or affiliation with a monarch, such as through service, governance, lineage, or formal association.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcc8a0481909c35161336bdfbf9 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.