Triple
T37788359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebastjan |
E942016
|
entity |
| Predicate | hasNameDayInSloveneTradition |
P200798
|
FINISHED |
| Object | January 20 |
—
|
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: January 20 | Statement: [Sebastjan, hasNameDayInSloveneTradition, January 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayInSloveneTradition Context triple: [Sebastjan, hasNameDayInSloveneTradition, January 20]
-
A.
hasNameDayInItalianTradition
Indicates that, according to Italian cultural or religious tradition, an entity’s name day is celebrated on a specified date.
-
B.
hasNameDayInSomeCountriesFor
Indicates that an entity is celebrated with a name day, in at least some countries, on behalf of or in relation to another specified entity.
-
C.
localNameInSlovene
Indicates the name by which something is locally known or referred to in the Slovene language.
-
D.
nameDayInSlovakia
Indicates that a person’s given name is celebrated on a specific name day according to the Slovak name-day calendar.
-
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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
| PDg | Predicate description generation | batch_69ffacdea2408190949dba9edeca4412 |
completed | May 9, 2026, 9:53 p.m. |
Created at: May 3, 2026, 4:19 p.m.