Triple
T31064101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillel II |
E791621
|
entity |
| Predicate | successorCalendarUsage |
P108742
|
FINISHED |
| Object | Hebrew calendar still in use in contemporary Judaism |
—
|
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: Hebrew calendar still in use in contemporary Judaism | Statement: [Hillel II, successorCalendarUsage, Hebrew calendar still in use in contemporary Judaism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorCalendarUsage Context triple: [Hillel II, successorCalendarUsage, Hebrew calendar still in use in contemporary Judaism]
-
A.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
calendarIntroducedOn
Indicates the date on which a particular calendar system was first introduced or put into use.
-
C.
calendarUsedFor
Indicates that a particular calendar is employed or applied for a specific purpose, context, or activity.
-
D.
followsCalendarOf
chosen
Indicates that one entity adopts and adheres to the scheduling, events, or time structure defined by another entity’s calendar.
-
E.
predecessorCalendar
Indicates that one calendar immediately precedes another in a defined chronological or version sequence.
- 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_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: April 29, 2026, 9:01 p.m.