Triple
T7026062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur |
E162948
|
entity |
| Predicate | etymologyHint |
P453
|
FINISHED |
| Object | derived from the given name Arthur |
—
|
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: derived from the given name Arthur | Statement: [Arthur, etymologyHint, derived from the given name Arthur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyHint Context triple: [Arthur, etymologyHint, derived from the given name Arthur]
-
A.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
B.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
C.
etymology
chosen
Indicates the historical origin and development of a word or term, including its source language and form.
-
D.
etymologyTheme
Indicates that something (such as a word, name, or term) has its origin, derivation, or linguistic history related to a particular theme, source, or conceptual basis.
-
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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.