Triple

T7892715
Position Surface form Disambiguated ID Type / Status
Subject Lystra E183272 entity
Predicate locatedNear P294 FINISHED
Object Derbe E478895 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: Derbe | Statement: [Lystra, locatedNear, Derbe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Derbe
Context triple: [Lystra, locatedNear, Derbe]
  • A. Derbe chosen
    Derbe was an ancient city in the region of Lycaonia in Asia Minor, known from the New Testament as a place visited by Paul and his companions during their missionary journeys.
  • B. Durbach
    Durbach is a wine-growing municipality in southwestern Germany, renowned for its vineyards and picturesque location in the Black Forest region.
  • C. Todenfeld
    Todenfeld is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
  • D. Tarusa
    Tarusa is a small historic town in western Russia known for its scenic location on the Oka River and its associations with Russian artists and writers.
  • E. Dömitz
    Dömitz is a small historic town in northern Germany, known for its well-preserved fortress and location on the Elbe River near the former inner-German border.
  • 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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb39fef2e48190a6282c217c33c57a completed March 31, 2026, 3:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5ba51ee48190b654a931da2c049f completed March 31, 2026, 5:29 a.m.
Created at: March 30, 2026, 5 p.m.