Triple
T17810881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Nassau-Saarbrücken |
E444698
|
entity |
| Predicate | typeOfMonarchyInTerritories |
P21959
|
FINISHED |
| Object | county |
—
|
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: county | Statement: [House of Nassau-Saarbrücken, typeOfMonarchyInTerritories, county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMonarchyInTerritories Context triple: [House of Nassau-Saarbrücken, typeOfMonarchyInTerritories, county]
-
A.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
B.
typeOfMonarchyTitle
Indicates that a given title is a specific type or category of monarchy-related title (e.g., king, queen, emperor) within a monarchical system.
-
C.
governingMonarchyAtCreation
Indicates the monarchy that held governing authority over an entity at the time the entity was created.
-
D.
monarchy
Indicates a system of governance in which supreme authority is vested in a single ruler, typically a king or queen, whose position is usually hereditary.
-
E.
monarchType
chosen
Indicates the specific kind or category of monarchy or monarch associated with an 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887b5e50819098506f0b92d709b5 |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.