Triple
T31282288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Origo Gentis Langobardorum |
E797702
|
entity |
| Predicate | explainsEtymologyOf |
P453
|
FINISHED |
| Object | name of the Lombards |
—
|
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: name of the Lombards | Statement: [Origo Gentis Langobardorum, explainsEtymologyOf, name of the Lombards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explainsEtymologyOf Context triple: [Origo Gentis Langobardorum, explainsEtymologyOf, name of the Lombards]
-
A.
etymologyContext
Indicates the contextual or situational background (such as time, place, culture, or domain) relevant to the origin and historical development of a word or term.
-
B.
etymologyPossibleMeaning
Indicates a possible or hypothesized meaning that an etymological analysis suggests for a word or term.
-
C.
etymology
chosen
Indicates the historical origin and development of a word or term, including its source language and form.
-
D.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
E.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.