Triple
T15100523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiwaz rune |
E360650
|
entity |
| Predicate | positionInFuthark |
P117323
|
FINISHED |
| Object | 17th rune of the Elder Futhark |
—
|
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: 17th rune of the Elder Futhark | Statement: [Tiwaz rune, positionInFuthark, 17th rune of the Elder Futhark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInFuthark Context triple: [Tiwaz rune, positionInFuthark, 17th rune of the Elder Futhark]
-
A.
languageFamilyPosition
Indicates the hierarchical position or role that a language occupies within its broader language family structure.
-
B.
positionInField
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionOnLanguage
Indicates the stance, opinion, or viewpoint that an entity holds regarding a particular language.
-
E.
positionInText
Indicates the specific location or span that something occupies within a text.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00550007481909e02ee1d597a4d37 |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:04 a.m.