Triple

T13158959
Position Surface form Disambiguated ID Type / Status
Subject Leipsoi E312670 entity
Predicate officialName P66 FINISHED
Object Leipsoi E312670 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: Leipsoi | Statement: [Leipsoi, officialName, Leipsoi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leipsoi
Context triple: [Leipsoi, officialName, Leipsoi]
  • A. Leipsoi chosen
    Leipsoi is a small, tranquil Greek island in the Dodecanese known for its traditional villages, clear waters, and unspoiled natural scenery.
  • B. Leisnig
    Leisnig is a small historic town in the German state of Saxony, known for its medieval architecture and the prominent Mildenstein Castle overlooking the Mulde River.
  • C. Lankwitz
    Lankwitz is a residential locality in the southwestern part of Berlin, known for its quiet neighborhoods, green spaces, and mix of historic and modern architecture.
  • D. Köppern
    Köppern is a district of the town of Friedrichsdorf in the Hochtaunus region of Hesse, Germany.
  • E. Markranstädt
    Markranstädt is a small town in the German state of Saxony, located near Leipzig and known for its local industry and proximity to the Kulkwitzer See recreation area.
  • 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_69d806ac3ee081909b2fd27d060aa974 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98c0971008190869e9de710f4c579 completed April 10, 2026, 11:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6eaf2ae688190b3484989791977ce completed May 3, 2026, 6:28 a.m.
Created at: April 9, 2026, 9:12 p.m.