Triple
T21591633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quintilis |
E532795
|
entity |
| Predicate | preJulianCalendarPosition |
P29015
|
FINISHED |
| Object | fifth month |
—
|
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: fifth month | Statement: [Quintilis, preJulianCalendarPosition, fifth month]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preJulianCalendarPosition Context triple: [Quintilis, preJulianCalendarPosition, fifth month]
-
A.
positionInGregorianCalendar
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
-
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.
positionInRomanCalendar
chosen
Indicates the ordinal placement or rank that something occupies within the sequence of months or days in the Roman calendar.
-
E.
frenchRepublicanCalendarPosition
Indicates the position or placement of something within the structure of the French Republican Calendar (such as its specific day, month, or date slot).
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefaddc8508190950b31e2df865ad1 |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.