Triple
T8916135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mixed constitution (Sparta) |
E212300
|
entity |
| Predicate | monarchicalPowerExercisedBy |
P86362
|
FINISHED |
| Object | two hereditary kings |
—
|
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: two hereditary kings | Statement: [mixed constitution (Sparta), monarchicalPowerExercisedBy, two hereditary kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchicalPowerExercisedBy Context triple: [mixed constitution (Sparta), monarchicalPowerExercisedBy, two hereditary kings]
-
A.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
B.
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.
-
C.
confersPowerOnMonarch
Indicates that one entity grants or bestows governing authority or ruling power upon a monarch.
-
D.
commandingMonarch
Indicates that one entity is the ruling monarch who issues orders or exercises authoritative command over another entity.
-
E.
monarchSheIsHeirTo
Indicates that the subject is the designated heir to the specified monarch’s throne or title.
- F. None of above. chosen
Provenance (4 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc660f6a088190b0af829ea809d8ad |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.