Triple

T13978288
Position Surface form Disambiguated ID Type / Status
Subject Nkroful E336240 entity
Predicate locatedNear P294 FINISHED
Object Axim E577141 NE 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: Axim | Statement: [Nkroful, locatedNear, Axim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Axim
Context triple: [Nkroful, locatedNear, Axim]
  • A. Axim chosen
    Axim is a coastal town in southwestern Ghana known for its historic forts, fishing industry, and beaches along the Atlantic Ocean.
  • B. Axius
    Axius is the ancient name of the Orontes River, a historically significant waterway in the Near East that flows through modern-day Lebanon, Syria, and Turkey.
  • C. Alixan
    Alixan is a commune in southeastern France, near Valence in the Drôme department, known for hosting the Valence TGV high-speed rail station.
  • D. Axieros
    Axieros is an ancient mystery goddess, often identified with Demeter, venerated at the Sanctuary of the Great Gods on the island of Samothrace.
  • E. Axamo
    Axamo is a locality in Jönköping Municipality in southern Sweden, known primarily for its proximity to Jönköping Airport.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d81c639e808190a0e4b4f3d31c6a59 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e9fc7248190a9f26e253286ac3c completed April 14, 2026, 12:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fba1e3cafc8190a1806a29b2e46ae9 completed May 6, 2026, 8:17 p.m.
Created at: April 9, 2026, 10:18 p.m.