Triple
T24294924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safar |
E605930
|
entity |
| Predicate | hasNoFixedGregorianDates |
P155447
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Safar, hasNoFixedGregorianDates, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoFixedGregorianDates Context triple: [Safar, hasNoFixedGregorianDates, true]
-
A.
doesNotUseLeapMonths
Indicates that the referenced calendar or timekeeping system does not incorporate leap months to adjust for discrepancies between its cycle and the astronomical year.
-
B.
hasGregorianDateRange
Indicates that an entity is associated with a specific start and end date expressed in the Gregorian calendar.
-
C.
hasDateInGregorianCalendar
Indicates that an entity is associated with a specific date expressed using the Gregorian calendar system.
-
D.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
E.
hasDateInJulianCalendar
Indicates that an entity is associated with a specific date expressed according to the Julian calendar system.
- F. None of above. chosen
Provenance (4 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f291593c0881908a6827f0d8899fe6 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:09 a.m.