Triple
T2192671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King's Commissioner |
E49897
|
entity |
| Predicate | titleDependsOnMonarchGender |
P13876
|
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: [King's Commissioner, titleDependsOnMonarchGender, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleDependsOnMonarchGender Context triple: [King's Commissioner, titleDependsOnMonarchGender, true]
-
A.
monarchTitleGenderedForm
chosen
Indicates the specific gendered version of a monarch’s title (e.g., king vs. queen) used to refer to that ruler.
-
B.
lyricsChangeWithMonarchGender
Indicates that the lyrics of something (such as a song or anthem) are altered depending on whether the reigning monarch is male or female.
-
C.
monarchRole
Indicates that an entity holds or is assigned the role, office, or position of a monarch in relation to a state or domain.
-
D.
monarchType
Indicates the specific kind or category of monarchy or monarch associated with an entity.
-
E.
monarchRelativeRole
Indicates the specific familial or relational role an individual holds in connection to a monarch (such as consort, heir, sibling, or other royal relative).
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf48ceb48190956df39377df0548 |
completed | March 7, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.