Triple
T9527378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirin |
E229793
|
entity |
| Predicate | nameDayStatus |
P88558
|
FINISHED |
| Object | no widely recognized name day |
—
|
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: no widely recognized name day | Statement: [Shirin, nameDayStatus, no widely recognized name day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameDayStatus Context triple: [Shirin, nameDayStatus, no widely recognized name day]
-
A.
nameDayExists
Indicates that there exists a recognized name day associated with a given name (and possibly date or locale).
-
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
Indicates a calendar system that specifies which personal names are celebrated on particular days (name days).
-
D.
nameStatus
Indicates the status or condition associated with an entity’s name, such as whether it is current, preferred, alternate, or deprecated.
-
E.
hasNameDay
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd989c831081908877e42f7ead84ba |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89f1d748190bf3636bea28d8a37 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 8 p.m.