Triple
T5336659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illyrius |
E123842
|
entity |
| Predicate | nameEtymologyRelation |
P30589
|
FINISHED |
| Object | source of the name of the Illyrians |
—
|
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: source of the name of the Illyrians | Statement: [Illyrius, nameEtymologyRelation, source of the name of the Illyrians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameEtymologyRelation Context triple: [Illyrius, nameEtymologyRelation, source of the name of the Illyrians]
-
A.
etymologyRelatesTo
chosen
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
-
B.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
C.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
D.
nameCognateOf
Indicates that two names share a common linguistic origin or form, typically due to derivation from the same root or historical source.
-
E.
etymologyReason
Indicates the reason, source, or origin explaining how or why a term acquired its particular etymology.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85b104c081908b81236a0142e1c8 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.