Triple
T33798884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Micklethwaite |
E866154
|
entity |
| Predicate | hasOnomasticElementOrigin |
P143350
|
FINISHED |
| Object | Old Norse |
—
|
NE NERFINISHED |
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 Norse | Statement: [Micklethwaite, hasOnomasticElementOrigin, Old Norse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnomasticElementOrigin Context triple: [Micklethwaite, hasOnomasticElementOrigin, Old Norse]
-
A.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
hasOnomasticRelation
Indicates that there is a relationship between entities based on names, naming patterns, or shared onomastic (name-related) features.
-
C.
hasNameEtymologyIn
chosen
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
D.
hasEthnolinguisticOriginOfToponym
Indicates that a toponym (place name) originates from or is derived from a particular ethnolinguistic group or language.
-
E.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:46 a.m.