Triple
T3755092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burmese calendar |
E82026
|
entity |
| Predicate | yearOneReference |
P10626
|
FINISHED |
| Object | 638 CE |
—
|
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: 638 CE | Statement: [Burmese calendar, yearOneReference, 638 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOneReference Context triple: [Burmese calendar, yearOneReference, 638 CE]
-
A.
eraYearOne
chosen
Indicates that the referenced year is designated as the first year of a particular era or calendrical system.
-
B.
yearDescribed
Indicates the year in which something (typically a species, object, or concept) was formally described or documented.
-
C.
yearDescribedAs
Indicates the specific year in which something was formally characterized, documented, or described.
-
D.
yearZero
Indicates that the referenced year is designated as the starting point (year 0) of a particular calendar, timeline, or counting system.
-
E.
frontiersReferenceYear
Indicates the specific year to which a given Frontiers reference or citation pertains.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb94ffc08190a7fd1ce71a15f787 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.