Triple
T21709454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maius |
E535860
|
entity |
| Predicate | preJulianStatus |
P145044
|
FINISHED |
| Object | month of the pre-Julian Roman calendar |
—
|
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: month of the pre-Julian Roman calendar | Statement: [Maius, preJulianStatus, month of the pre-Julian Roman calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preJulianStatus Context triple: [Maius, preJulianStatus, month of the pre-Julian Roman calendar]
-
A.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
B.
accuracyComparedToJulian
Indicates how the accuracy of something compares to that of the Julian calendar as a reference standard.
-
C.
preTridentineStatus
Indicates the status or condition of something in relation to the period before the Council of Trent (i.e., prior to Tridentine reforms).
-
D.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
-
E.
isLunisolar
Indicates that something is based on or determined by both the cycles of the moon and the sun.
- F. None of above. chosen
Provenance (4 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5321d34819091f3cd03f7b407c0 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:46 p.m.