Triple

T582190
Position Surface form Disambiguated ID Type / Status
Subject Kislev E15081 entity
Predicate timeSystem P15775 FINISHED
Object based on lunar months adjusted to solar year 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: based on lunar months adjusted to solar year | Statement: [Kislev, timeSystem, based on lunar months adjusted to solar year]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeSystem
Context triple: [Kislev, timeSystem, based on lunar months adjusted to solar year]
  • A. usesClockSystem
    Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
  • B. timeType
    Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
  • C. time
    Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
  • D. timeNotation
    Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
  • E. timeOffsetReference
    Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
  • 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_69a4935783b8819082b77726ec10cc42 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49b85becc8190b4d98c00e5fa7c04 completed March 1, 2026, 8:03 p.m.
PD Predicate disambiguation batch_69a494c7f9008190bd8d05b4dc2a7c7f completed March 1, 2026, 7:34 p.m.
PDg Predicate description generation batch_69a4985a2d08819090947895d9439e06 completed March 1, 2026, 7:49 p.m.
Created at: March 1, 2026, 7:33 p.m.