Triple
T31064092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillel II |
E791621
|
entity |
| Predicate | calendarFeatureIntroduced |
P170707
|
FINISHED |
| Object | fixed cycle of leap years |
—
|
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: fixed cycle of leap years | Statement: [Hillel II, calendarFeatureIntroduced, fixed cycle of leap years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarFeatureIntroduced Context triple: [Hillel II, calendarFeatureIntroduced, fixed cycle of leap years]
-
A.
calendarIntroducedOn
Indicates the date on which a particular calendar system was first introduced or put into use.
-
B.
introducedFeatureCategory
Indicates that an entity caused a particular feature category to be created, presented, or made available for the first time.
-
C.
calendarFeature
Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
-
D.
serviceIntroduced
Indicates that a particular service has been launched, made available, or brought into operation at a certain time or context.
-
E.
featureOfReleases
Indicates that certain features are associated with, included in, or introduced as part of specific releases.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695792b748190882e715603d406a2 |
completed | May 3, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 9:01 p.m.