Triple
T30168994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umma |
E766866
|
entity |
| Predicate | usedCalendarType |
P5453
|
FINISHED |
| Object | lunar calendar |
—
|
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: lunar calendar | Statement: [Umma, usedCalendarType, lunar calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCalendarType Context triple: [Umma, usedCalendarType, lunar calendar]
-
A.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
usedInCalendarSystem
Indicates that something (such as a time unit, era, or convention) is employed as part of a particular calendar system.
-
C.
calendarType
chosen
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
D.
usedCalendarReform
Indicates that one entity adopted or implemented a particular calendar reform associated with another entity.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:24 p.m.