Triple
T36948507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec calendar |
E913985
|
entity |
| Predicate | hasSolarYearLength |
P71812
|
FINISHED |
| Object | 365 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 days | Statement: [Aztec calendar, hasSolarYearLength, 365 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSolarYearLength Context triple: [Aztec calendar, hasSolarYearLength, 365 days]
-
A.
hasSolarCalendarLength
chosen
Indicates that an entity’s solar calendar is characterized by a specific duration or number of days.
-
B.
hasSolarDayLength
Indicates that an entity is associated with a specific duration for one complete solar day (the time between successive noons).
-
C.
hasAverageYearLength
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
-
D.
hasSolarCycle_length_years
Indicates the duration of an entity’s solar activity cycle measured in years.
-
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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 4:13 p.m.