Triple
T3475710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statuto Albertino |
E73369
|
entity |
| Predicate | kingPowers |
P49192
|
FINISHED |
| Object | right to appoint and dismiss ministers |
—
|
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: right to appoint and dismiss ministers | Statement: [Statuto Albertino, kingPowers, right to appoint and dismiss ministers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingPowers Context triple: [Statuto Albertino, kingPowers, right to appoint and dismiss ministers]
-
A.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
B.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
C.
capitalDuringReign
Indicates that a particular city or location served as the capital of a political entity during the reign of a specified ruler.
-
D.
kingdom
Indicates that an entity is classified within a particular biological kingdom in a taxonomic hierarchy.
-
E.
alsoKingOf
Indicates that an entity who is king of one place is simultaneously king of another place as well.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb593a388190b7786190deba96ed |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:17 p.m.