Triple
T3159880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iyar |
E66075
|
entity |
| Predicate | hasNumericValueInHebrewCalendar |
P44420
|
FINISHED |
| Object | 2 (religious 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: 2 (religious year) | Statement: [Iyar, hasNumericValueInHebrewCalendar, 2 (religious year)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumericValueInHebrewCalendar Context triple: [Iyar, hasNumericValueInHebrewCalendar, 2 (religious year)]
-
A.
representsNumberInHebrewNumerals
Indicates that one entity is used to represent the numerical value of another entity using Hebrew numeral notation.
-
B.
hasNumericValueInGreekNumerals
Indicates that an entity is associated with a specific numeric value expressed using Greek numeral notation.
-
C.
hasArabicNumeral
Indicates that an entity is associated with, represented by, or expressed using an Arabic numeral.
-
D.
dateInHebrewCalendar
Indicates that a specific date is expressed according to the Hebrew (Jewish) calendar system rather than another calendar.
-
E.
hasNumericalValue
chosen
Indicates that an entity is associated with a specific numeric quantity or measurement.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada61606bc8190a8ad760d680924eb |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.