Triple
T11925766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronation of Charles I |
E283778
|
entity |
| Predicate | hasGregorianYear |
P61142
|
FINISHED |
| Object | 1626 |
—
|
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: 1626 | Statement: [Coronation of Charles I, hasGregorianYear, 1626]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGregorianYear Context triple: [Coronation of Charles I, hasGregorianYear, 1626]
-
A.
hasApproxGregorianStart
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
-
B.
hasDateInGregorianCalendar
Indicates that an entity is associated with a specific date expressed using the Gregorian calendar system.
-
C.
yearInGregorianCalendar
chosen
Indicates that a specified year is measured according to the Gregorian calendar system.
-
D.
hasDateInJulianCalendar
Indicates that an entity is associated with a specific date expressed according to the Julian calendar system.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e3ff308190851ce656286bc67e |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.