Triple
T11241891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya calendar |
E266090
|
entity |
| Predicate | LongCountBaseDate |
P16736
|
FINISHED |
| Object | August 11, 3114 BCE (proleptic Gregorian) |
—
|
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: August 11, 3114 BCE (proleptic Gregorian) | Statement: [Maya calendar, LongCountBaseDate, August 11, 3114 BCE (proleptic Gregorian)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LongCountBaseDate Context triple: [Maya calendar, LongCountBaseDate, August 11, 3114 BCE (proleptic Gregorian)]
-
A.
hasDayCount
Indicates that an entity is associated with a specific number of days, expressing the duration or count of days related to it.
-
B.
calculationStartDate
Indicates the date on which a particular calculation or computation process begins.
-
C.
hasDayCountCommonYear
Indicates that something has a specified number of days as it occurs in a common (non-leap) year.
-
D.
calendarEpoch
chosen
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
E.
hasNumberOfDaysIn13thMonth
Indicates the specific count of days that occur in the thirteenth month of a given calendar or time system.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e919eaf48190a1457851cfc56afb |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:30 p.m.