Triple
T582200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kislev |
E15081
|
entity |
| Predicate | chronologicalFunction |
P15777
|
FINISHED |
| Object | organizing Jewish 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: organizing Jewish year | Statement: [Kislev, chronologicalFunction, organizing Jewish year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalFunction Context triple: [Kislev, chronologicalFunction, organizing Jewish year]
-
A.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
C.
historicalFunction
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
D.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
E.
workChronologyPosition
Indicates the relative ordering or position of a work within a sequence of works, such as in a career, series, or catalog.
- 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.