Triple
T2100993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morea |
E37090
|
entity |
| Predicate | etymologyHypothesis |
P15774
|
FINISHED |
| Object | derived from Greek word for mulberry (morea) |
—
|
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 Greek word for mulberry (morea) | Statement: [Morea, etymologyHypothesis, derived from Greek word for mulberry (morea)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyHypothesis Context triple: [Morea, etymologyHypothesis, derived from Greek word for mulberry (morea)]
-
A.
etymology
Indicates the historical origin and development of a word or term, including its source language and form.
-
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.
etymologyPossibleMeaning
chosen
Indicates a possible or hypothesized meaning that an etymological analysis suggests for a word or term.
-
E.
etymologyRelatesTo
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabb512c819087b1d5ec8ef11e63 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.