Triple
T28354677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blanka |
E718191
|
entity |
| Predicate | hasNameDayInCzechCalendar |
P68495
|
FINISHED |
| Object | October 25 |
—
|
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: October 25 | Statement: [Blanka, hasNameDayInCzechCalendar, October 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayInCzechCalendar Context triple: [Blanka, hasNameDayInCzechCalendar, October 25]
-
A.
nameDayInCzech
chosen
Indicates that a person’s name corresponds to a specific nameday date in the Czech calendar.
-
B.
hasNameDay
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
-
C.
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.
-
D.
hasNameDayInformation
Indicates that there exists associated information about a person’s name day, such as the date or related observances.
-
E.
nameDayInSlovakia
Indicates that a person’s given name is celebrated on a specific name day according to the Slovak name-day calendar.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 28, 2026, 12:48 a.m.