Triple
T35419194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florestan I, Prince of Monaco |
E1023732
|
entity |
| Predicate | reignImpact |
P55427
|
FINISHED |
| Object | weakening of the Principality of 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: weakening of the Principality of Monaco | Statement: [Florestan I, Prince of Monaco, reignImpact, weakening of the Principality of Monaco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignImpact Context triple: [Florestan I, Prince of Monaco, reignImpact, weakening of the Principality of Monaco]
-
A.
impactOnMonarch
chosen
Indicates a relationship where an action, event, or condition produces an effect or consequence on a monarch.
-
B.
reignIs
Indicates that one entity holds ruling authority or sovereignty over another for a specified period.
-
C.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
D.
reignAfter
Indicates that one entity begins its reign or rule following the conclusion of another entity's reign.
-
E.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:03 p.m.