Triple
T31064095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillel II |
E791621
|
entity |
| Predicate | calendarImpact |
P26069
|
FINISHED |
| Object | standardization of Jewish festival dates |
—
|
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: standardization of Jewish festival dates | Statement: [Hillel II, calendarImpact, standardization of Jewish festival dates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarImpact Context triple: [Hillel II, calendarImpact, standardization of Jewish festival dates]
-
A.
calendarContribution
chosen
Indicates a relationship where an entity adds to, modifies, or otherwise participates in the creation or maintenance of a calendar or scheduled events.
-
B.
calendarDependence
Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
-
C.
calendarVariesBy
Indicates that the characteristics or values of a calendar (such as dates, events, or structure) change depending on another specified factor or context.
-
D.
calendarFocus
Indicates that attention or interaction is currently directed toward a particular calendar or calendar-related view.
-
E.
calendarFeature
Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:01 p.m.