Triple
T14987060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ireneusz |
E373731
|
entity |
| Predicate | ultimateEtymology |
P506
|
FINISHED |
| Object | Greek word "eirēnē" |
—
|
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: Greek word "eirēnē" | Statement: [Ireneusz, ultimateEtymology, Greek word "eirēnē"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimateEtymology Context triple: [Ireneusz, ultimateEtymology, Greek word "eirēnē"]
-
A.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
-
B.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
C.
etymologicalField
Indicates that one term belongs to a particular semantic or conceptual domain relevant to its etymological origin or historical development.
-
D.
traditionalEtymology
Indicates that an entity’s origin or meaning is explained according to a historically established or customary etymological account.
-
E.
etymologicalLanguage
chosen
Indicates the language from which a word or term is historically derived in its 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7007588819095bb1de029a6f2eb |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:52 a.m.