Triple
T33388246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya area |
E854977
|
entity |
| Predicate | developedCalendarSystem |
P64770
|
FINISHED |
| Object | Maya calendar |
—
|
NE NERFINISHED |
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: Maya calendar | Statement: [Maya area, developedCalendarSystem, Maya calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedCalendarSystem Context triple: [Maya area, developedCalendarSystem, Maya calendar]
-
A.
hadDayCountingSystem
chosen
Indicates that an entity used or maintained a specific system for counting or organizing days.
-
B.
introducedWritingSystem
Indicates that an entity is responsible for originating or bringing a particular writing system into use.
-
C.
eraChronology
Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
-
D.
writingSystemDevelopedFrom
Indicates that one writing system originated, evolved, or was derived from another earlier writing system.
-
E.
firstDeveloped
Indicates that one entity was the earliest to create, originate, or bring another entity into existence.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:35 a.m.