Triple

T16579495
Position Surface form Disambiguated ID Type / Status
Subject Augustan wars E402798 entity
Predicate hasLocation P40 FINISHED
Object Leuke Kome E202445 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: Leuke Kome | Statement: [Augustan wars, hasLocation, Leuke Kome]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leuke Kome
Context triple: [Augustan wars, hasLocation, Leuke Kome]
  • A. Leuke Kome chosen
    Leuke Kome was an important Nabataean Red Sea port settlement that served as a key hub for trade between Arabia, Egypt, and the Mediterranean world.
  • B. Le Kram
    Le Kram is a coastal town and suburb of Tunis in northeastern Tunisia, known for its proximity to the capital and the Gulf of Tunis.
  • C. Koekange
    Koekange is a village in the Dutch province of Drenthe, located within the municipality of De Wolden.
  • D. Houttuin
    Houttuin is a town in Suriname located within the Wanica District, known primarily as a residential and semi-rural community near the capital region.
  • E. Vriezekoop
    Vriezekoop is a small village in the Dutch province of South Holland, known for its rural character and location along the Westeinderplassen near Leimuiden.
  • 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3595f9be88190b01ba628ecf1103d completed April 18, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a006eee7e4881908a529717bc449078 completed May 10, 2026, 11:41 a.m.
Created at: April 10, 2026, 5:16 a.m.