Triple
T13620449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign Prince of Monaco |
E325434
|
entity |
| Predicate | firstHolderStartReign |
P1506
|
FINISHED |
| Object | 1604 |
—
|
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: 1604 | Statement: [Sovereign Prince of Monaco, firstHolderStartReign, 1604]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderStartReign Context triple: [Sovereign Prince of Monaco, firstHolderStartReign, 1604]
-
A.
firstMonarchOfCurrentDynastyReignStart
Indicates the date or time when the reign of the first monarch of the current ruling dynasty began.
-
B.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
C.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
D.
reignAsCoRulerStart
Indicates the time or event when an entity begins to exercise ruling authority jointly with one or more other rulers.
-
E.
firstCoronationHeldFor
Indicates that a particular entity was the subject or beneficiary of the first coronation event associated with 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.