Triple
T21918287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mausolus |
E541235
|
entity |
| Predicate | etymologicalLegacy |
P453
|
FINISHED |
| Object | term "mausoleum" derived from his name |
—
|
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: term "mausoleum" derived from his name | Statement: [Mausolus, etymologicalLegacy, term "mausoleum" derived from his name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologicalLegacy Context triple: [Mausolus, etymologicalLegacy, term "mausoleum" derived from his name]
-
A.
etymologicalField
Indicates that one term belongs to a particular semantic or conceptual domain relevant to its etymological origin or historical development.
-
B.
etymology
chosen
Indicates the historical origin and development of a word or term, including its source language and form.
-
C.
traditionalEtymology
Indicates that an entity’s origin or meaning is explained according to a historically established or customary etymological account.
-
D.
etymologicalLanguage
Indicates the language from which a word or term is historically derived in its etymology.
-
E.
etymologicalNote
Indicates that there is a note explaining the origin, historical development, or source language of a 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233924008190923724d0c0f2d435 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:43 p.m.