Triple
T21709528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ianuarius |
E535863
|
entity |
| Predicate | typicalLengthInJulianCalendar |
P6443
|
FINISHED |
| Object | 31 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: 31 days | Statement: [Ianuarius, typicalLengthInJulianCalendar, 31 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLengthInJulianCalendar Context triple: [Ianuarius, typicalLengthInJulianCalendar, 31 days]
-
A.
hasAverageYearLength
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
-
B.
hasAverageMonthLength
chosen
Indicates that an entity is associated with a specified average length of a month, typically expressed in days.
-
C.
HaabʼLength
Indicates the duration or number of days that a Haabʼ calendar period (such as a month or cycle) spans.
-
D.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
E.
accuracyComparedToTropicalYear
Indicates how closely something’s measured or defined duration matches the length of a tropical year.
- 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_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. |
Created at: April 16, 2026, 6:46 p.m.