Triple
T26570262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ylva |
E666803
|
entity |
| Predicate | hasNameDayDateInSweden |
P76668
|
FINISHED |
| Object | January 12 |
—
|
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 12 | Statement: [Ylva, hasNameDayDateInSweden, January 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayDateInSweden Context triple: [Ylva, hasNameDayDateInSweden, January 12]
-
A.
nameDayDateInSweden
chosen
Indicates the specific calendar date in Sweden on which a given person’s name day is celebrated.
-
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.
nameInSwedish
Indicates that an entity is known or referred to by a particular name when expressed in the Swedish language.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 1:57 a.m.