Triple

T13257378
Position Surface form Disambiguated ID Type / Status
Subject Langden E315693 entity
Predicate likelyDerivedFrom P909 FINISHED
Object Old English elements for "long" and "hill" or "valley" 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: Old English elements for "long" and "hill" or "valley" | Statement: [Langden, likelyDerivedFrom, Old English elements for "long" and "hill" or "valley"]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: likelyDerivedFrom
Context triple: [Langden, likelyDerivedFrom, Old English elements for "long" and "hill" or "valley"]
  • A. derivedFrom chosen
    Indicates that one entity originates, is obtained, or is developed from another source entity.
  • B. inheritedFrom
    Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
  • C. derivedBy
    Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
  • D. notDerivedFrom
    Indicates that one entity is explicitly not obtained, inferred, or produced from another entity.
  • E. developedFrom
    Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
  • 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_69d806b1d9ac8190852c5571d5bd5f0f completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99cfdc9388190af1fdd3cd4717bd8 completed April 11, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69d98f60911081909fa346a054f76c9f completed April 11, 2026, 12:01 a.m.
Created at: April 9, 2026, 9:25 p.m.