Triple

T21051024
Position Surface form Disambiguated ID Type / Status
Subject Arki village E518581 entity
Predicate associatedWith P37 FINISHED
Object Arki NE NERFINISHED

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: Arki | Statement: [Arki village, associatedWith, Arki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arki
Context triple: [Arki village, associatedWith, Arki]
  • A. Arki
    Arki is a small, sparsely populated Greek island in the Aegean Sea, known for its quiet beaches and traditional fishing community.
  • B. Arki chosen
    Arki is a small town in the Solan district of Himachal Pradesh, India, known for its historic fort and scenic Himalayan surroundings.
  • C. Arke
    Arke was a Dutch leisure airline and tour operator brand that later became part of TUI and was rebranded as TUI fly Netherlands.
  • D. Aru
    Aru is a town in the northeastern Democratic Republic of the Congo, near the Ugandan border, serving as a local administrative and trading center in Ituri Province.
  • E. Aru
    Aru is a group of closely related Austronesian languages spoken primarily in the Aru Islands of eastern Indonesia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5053ac48190921529544959e906 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fd7bd96c81909cb46419ad4e1222 completed April 21, 2026, 4:30 a.m.
Created at: April 16, 2026, 2:35 p.m.