Triple
T11174474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Týr |
E264371
|
entity |
| Predicate | dayOfWeekEtymology |
P49014
|
FINISHED |
| Object | Old English Tiwesdæg |
—
|
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: Old English Tiwesdæg | Statement: [Týr, dayOfWeekEtymology, Old English Tiwesdæg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayOfWeekEtymology Context triple: [Týr, dayOfWeekEtymology, Old English Tiwesdæg]
-
A.
weekdayEtymologyOf
chosen
Indicates that one concept is the etymological source or origin of the name of a particular weekday.
-
B.
dayName
Indicates the specific name of the day of the week associated with a given date or time.
-
C.
calendarMonthNameOrigin
Indicates the historical or cultural source from which a calendar month’s name is derived.
-
D.
dayName7
Indicates that the relationship specifies the name of the seventh day of the week associated with a given day entity.
-
E.
etymologyTheme
Indicates that something (such as a word, name, or term) has its origin, derivation, or linguistic history related to a particular theme, source, or conceptual basis.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e897774c819088ebc7231cebfba6 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.