Triple
T34964249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | François Grimaldi |
E1008344
|
entity |
| Predicate | inceptionOfRule |
P21305
|
FINISHED |
| Object | Grimaldi rule over Monaco |
—
|
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: Grimaldi rule over Monaco | Statement: [François Grimaldi, inceptionOfRule, Grimaldi rule over Monaco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionOfRule Context triple: [François Grimaldi, inceptionOfRule, Grimaldi rule over Monaco]
-
A.
beganRule
Indicates that an entity started its period of ruling or governance over another entity or domain.
-
B.
startOfRule
chosen
Indicates that one element marks the beginning boundary or initial segment of a specified rule.
-
C.
startDateRule
Indicates the rule or condition that determines when something is allowed or required to start.
-
D.
initialEnactment
Indicates that an action, rule, or condition is being put into effect for the first time, marking its original enactment or coming into force.
-
E.
coRuleStart
Indicates the point in time or sequence at which two or more rules begin to apply or take effect together.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.