Triple
T32348477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markéta |
E826528
|
entity |
| Predicate | nameDayInCzechCalendar |
P68495
|
FINISHED |
| Object | July 13 |
—
|
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: July 13 | Statement: [Markéta, nameDayInCzechCalendar, July 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameDayInCzechCalendar Context triple: [Markéta, nameDayInCzechCalendar, July 13]
-
A.
nameDayInCzech
chosen
Indicates that a person’s name corresponds to a specific nameday date in the Czech calendar.
-
B.
nameDayInSlovakia
Indicates that a person’s given name is celebrated on a specific name day according to the Slovak name-day calendar.
-
C.
czechName
Indicates that an entity has a name in the Czech language, specifying the Czech-language form of its name.
-
D.
dayName
Indicates the specific name of the day of the week associated with a given date or time.
-
E.
nameDayInBulgaria
Indicates that an entity has a specific name day celebration according to Bulgarian name day traditions and 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 12:49 a.m.