Triple
T640747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adar I |
E16733
|
entity |
| Predicate | calendarFunction |
P17613
|
FINISHED |
| Object | intercalation to align lunar months with 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: intercalation to align lunar months with solar year | Statement: [Adar I, calendarFunction, intercalation to align lunar months with solar year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarFunction Context triple: [Adar I, calendarFunction, intercalation to align lunar months with solar year]
-
A.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
B.
calendarFamily
Indicates that two calendars are related as part of the same family or grouping, typically sharing common characteristics, structure, or origin.
-
C.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
D.
agendaItem
Indicates that something is an item or entry on a planned agenda or schedule of topics to be addressed.
-
E.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f0189b08190a584b744f36fa761 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df0de3c81909721eb391ec94031 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.