Triple
T25060918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinhas |
E627653
|
entity |
| Predicate | nameDayContext |
P83423
|
FINISHED |
| Object | Jewish liturgical calendar |
—
|
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: Jewish liturgical calendar | Statement: [Pinhas, nameDayContext, Jewish liturgical calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameDayContext Context triple: [Pinhas, nameDayContext, Jewish liturgical calendar]
-
A.
nameDayBaseForm
Indicates the base or canonical form of a name used specifically for name-day (saint’s day) associations or celebrations.
-
B.
namesDay
Indicates that one entity is the name assigned to a particular day (such as a weekday or holiday) associated with another entity.
-
C.
nameDayCalendar
chosen
Indicates a calendar system that specifies which personal names are celebrated on particular days (name days).
-
D.
nameDayStatus
Indicates the status or condition of a person's name day (e.g., whether it is set, active, upcoming, or celebrated).
-
E.
nameDayExists
Indicates that there exists a recognized name day associated with a given name (and possibly date or locale).
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:10 a.m.