Triple
T4634696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishaq |
E101499
|
entity |
| Predicate | hasNameDayContext |
P57867
|
FINISHED |
| Object | religious rather than secular naming |
—
|
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: religious rather than secular naming | Statement: [Ishaq, hasNameDayContext, religious rather than secular naming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayContext Context triple: [Ishaq, hasNameDayContext, religious rather than secular naming]
-
A.
hasNameDay
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
-
B.
nameDayExists
Indicates that there exists a recognized name day associated with a given name (and possibly date or locale).
-
C.
hasDayNameSystem
Indicates that an entity employs or is associated with a particular system for naming or designating days.
-
D.
nameDayRegion
Indicates the region or geographic area in which a particular name day is observed or recognized.
-
E.
hasRegionalHolidayName
Indicates that a regional holiday is associated with a specific name or designation used to refer to it.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a5ec8108190aeb1147a67bff057 |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:13 p.m.