Triple
T14095725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babylonian calendar |
E339248
|
entity |
| Predicate | approximateNumberOfMonthsPerYear |
P9860
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [Babylonian calendar, approximateNumberOfMonthsPerYear, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNumberOfMonthsPerYear Context triple: [Babylonian calendar, approximateNumberOfMonthsPerYear, 12]
-
A.
hasAverageMonthLength
Indicates that an entity is associated with a specified average length of a month, typically expressed in days.
-
B.
approximateTimeInYear
Indicates that one time-related entity represents an estimated or non-exact point or interval within a given year for another entity.
-
C.
hasMonthCount
chosen
Indicates a relationship where an entity is associated with a specific number of months.
-
D.
hasAverageYearLength
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
-
E.
leapMonthFrequencyApprox
Indicates how often leap months occur, expressed as an approximate frequency rather than an exact interval.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb7fb3c819083266dbe7e93aaff |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.