Triple

T13231683
Position Surface form Disambiguated ID Type / Status
Subject Kurram District E315034 entity
Predicate valleyNameEtymology P66669 FINISHED
Object named after Kurram River 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: named after Kurram River | Statement: [Kurram District, valleyNameEtymology, named after Kurram River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: valleyNameEtymology
Context triple: [Kurram District, valleyNameEtymology, named after Kurram River]
  • A. valleyNameDerivedFrom chosen
    Indicates that the name of a valley is derived from, or based on, another specified source (such as a person, place, language term, or feature).
  • B. reservoirNameEtymology
    Indicates the origin or source of a reservoir’s name, such as the historical, cultural, or linguistic reason it was given that name.
  • C. valleyDesignation
    Indicates that an entity is formally designated or classified as a valley in relation to a specified geographic or administrative context.
  • D. seaNameEtymology
    Indicates the origin or derivation of the name given to a particular sea.
  • E. toponymLiteralMeaning
    Indicates the literal or etymological meaning of a place name (toponym), describing what the name directly translates to or signifies.
  • 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_69d806affc688190a25b6ccc588e9c72 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98d34ff288190bdb550a019b7a470 completed April 10, 2026, 11:52 p.m.
PD Predicate disambiguation batch_69d98bcb21648190aef241de1e7887e2 completed April 10, 2026, 11:46 p.m.
Created at: April 9, 2026, 9:22 p.m.