Triple
T5558260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shevat |
E145701
|
entity |
| Predicate | occursInCalendarType |
P5453
|
FINISHED |
| Object | lunisolar |
—
|
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: lunisolar | Statement: [Shevat, occursInCalendarType, lunisolar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInCalendarType Context triple: [Shevat, occursInCalendarType, lunisolar]
-
A.
calendarType
chosen
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
B.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
C.
roleInCalendar
Indicates that an entity holds a specific role or function within the context of a particular calendar or scheduled event.
-
D.
belongsToCalendar
Indicates that an event or item is associated with and contained within a specific calendar.
-
E.
calendarDependence
Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201529a88190bf0135e032b048ea |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.