Triple
T15045954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Mecklenburg-Schwerin |
E379224
|
entity |
| Predicate | hereditaryTitleAbolished |
P49022
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [House of Mecklenburg-Schwerin, hereditaryTitleAbolished, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryTitleAbolished Context triple: [House of Mecklenburg-Schwerin, hereditaryTitleAbolished, 1918]
-
A.
abolishedAsSovereignTitle
chosen
Indicates that a particular sovereign title or rank has been officially discontinued and no longer exists as a recognized position of rule.
-
B.
coronationAbolished
Indicates that a formal coronation ceremony for a ruler or office has been officially discontinued or abolished.
-
C.
titleAbolishedBy
Indicates that a particular title or rank was formally eliminated or discontinued by a specified authority, event, or legal act.
-
D.
aristocraticTitlePassedTo
Indicates that an aristocratic title is transferred or inherited from one person to another.
-
E.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded830c3c08190a87b81abbbb75377 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.