Triple

T685438
Position Surface form Disambiguated ID Type / Status
Subject Elul E13273 entity
Predicate hasEtymologyTheory P6879 FINISHED
Object possibly derived from an Akkadian word for harvest or search 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: possibly derived from an Akkadian word for harvest or search | Statement: [Elul, hasEtymologyTheory, possibly derived from an Akkadian word for harvest or search]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEtymologyTheory
Context triple: [Elul, hasEtymologyTheory, possibly derived from an Akkadian word for harvest or search]
  • A. etymology
    Indicates the historical origin and development of a word or term, including its source language and form.
  • B. etymologyStatus chosen
    Indicates the status or reliability classification of an etymological explanation for a term or name.
  • C. etymologicalLanguage
    Indicates the language from which a word or term is historically derived in its etymology.
  • D. etymologyType
    Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
  • E. hasTitleEtymology
    Indicates that the origin or derivation of a title is based on, or explained by, another term, name, or linguistic 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_69a4933e0f98819097d22766c49b61b8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a0924dec8190bbbd2bb244f85211 completed March 1, 2026, 8:24 p.m.
PD Predicate disambiguation batch_69a49d1f0ccc819088c1527beabcb718 completed March 1, 2026, 8:10 p.m.
Created at: March 1, 2026, 7:36 p.m.