Triple
T19893983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal decree |
E478101
|
entity |
| Predicate | mayRegulate |
P29625
|
FINISHED |
| Object | succession |
—
|
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: succession | Statement: [Royal decree, mayRegulate, succession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayRegulate Context triple: [Royal decree, mayRegulate, succession]
-
A.
allowsRegulationOf
chosen
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
B.
regulateBy
Indicates that one entity exercises control, guidance, or governance over another entity’s behavior, operation, or state through rules, mechanisms, or constraints.
-
C.
alsoRegulates
Indicates that an entity not only has a primary regulatory effect on a target but additionally regulates that same target through another, supplementary regulatory relationship.
-
D.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
E.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659105d7481909131d9907ac0094b |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.