Triple
T1086892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revised Julian calendar |
E24072
|
entity |
| Predicate | yearLength |
P9857
|
FINISHED |
| Object | 365.242222 days |
—
|
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: 365.242222 days | Statement: [Revised Julian calendar, yearLength, 365.242222 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearLength Context triple: [Revised Julian calendar, yearLength, 365.242222 days]
-
A.
hasAverageYearLength
chosen
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
-
B.
hasAverageMonthLength
Indicates that an entity is associated with a specified average length of a month, typically expressed in days.
-
C.
yearType
Indicates the classification or category assigned to a specific year (e.g., academic, fiscal, calendar, leap).
-
D.
hasSolarCycle_length_years
Indicates the duration of an entity’s solar activity cycle measured in years.
-
E.
quarterLength
Indicates that one entity specifies the length or duration of a quarter (e.g., a time period or segment) 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b963161081908a523c8d63871652 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.