Triple
T33647148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coronation of Elizabeth of Russia |
E861989
|
entity |
| Predicate | hasJulianDate |
P70407
|
FINISHED |
| Object | 1742-04-14 |
—
|
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: 1742-04-14 | Statement: [coronation of Elizabeth of Russia, hasJulianDate, 1742-04-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJulianDate Context triple: [coronation of Elizabeth of Russia, hasJulianDate, 1742-04-14]
-
A.
hasDateInJulianCalendar
chosen
Indicates that an entity is associated with a specific date expressed according to the Julian calendar system.
-
B.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
C.
accuracyComparedToJulian
Indicates how the accuracy of something compares to that of the Julian calendar as a reference standard.
-
D.
preJulianStatus
Indicates the status or condition of something during the period before the adoption of the Julian calendar.
-
E.
hasDateInGregorianCalendar
Indicates that an entity is associated with a specific date expressed using the Gregorian calendar system.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:42 a.m.