Triple
T14761029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandomierz Piasts |
E346859
|
entity |
| Predicate | hereditaryMonarchy |
P48009
|
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: [Sandomierz Piasts, hereditaryMonarchy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryMonarchy Context triple: [Sandomierz Piasts, hereditaryMonarchy, true]
-
A.
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.
-
B.
dynasticInheritance
chosen
Indicates that rights, titles, or property are passed down through a family line according to established rules of succession.
-
C.
traditionalMonarchy
Indicates a system where a monarchy operates according to long-established customs, hereditary succession, and historical institutions rather than modern or codified reforms.
-
D.
monarchSheIsHeirTo
Indicates that the subject is the designated heir to the specified monarch’s throne or title.
-
E.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f207dc819088a53f717736a121 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.