Triple
T9636421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sailor King |
E232943
|
entity |
| Predicate | hasMonarchicalStyleOfReferent |
P51784
|
FINISHED |
| Object | His Majesty |
—
|
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: His Majesty | Statement: [Sailor King, hasMonarchicalStyleOfReferent, His Majesty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonarchicalStyleOfReferent Context triple: [Sailor King, hasMonarchicalStyleOfReferent, His Majesty]
-
A.
styleOfMonarchTitle
chosen
Indicates the specific formal style or wording used in the official title of a monarch.
-
B.
refersToMonarchOf
Indicates that one entity makes reference to, mentions, or designates the reigning monarch of a specified realm or polity.
-
C.
usedInMonarchy
Indicates that something is employed, practiced, or functions within the context of a monarchical system of government.
-
D.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
E.
monarchicalPowerExercisedBy
Indicates that monarchical authority or ruling power is exercised or carried out by a specified agent or entity.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b5045cc8190ab717f42d803e010 |
completed | April 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.