Triple

T16769031
Position Surface form Disambiguated ID Type / Status
Subject Syntyche E407541 entity
Predicate location P40 FINISHED
Object Philippi E47686 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: Philippi | Statement: [Syntyche, location, Philippi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Philippi
Context triple: [Syntyche, location, Philippi]
  • A. Philippi
    Philippi is a township in Cape Town, South Africa, known as part of the Cape Flats area characterized by dense residential communities and socio-economic challenges.
  • B. Philippi chosen
    Philippi was an ancient city in eastern Macedonia, notable in early Christianity as the site of one of the first European churches and a key location in the missionary journeys of the Apostle Paul.
  • C. Colossae
    Colossae was an ancient Phrygian city in Asia Minor, notable in early Christianity as the community addressed by the New Testament Epistle to the Colossians.
  • D. Troas
    Troas is an ancient historical region in northwestern Asia Minor, near the Aegean coast, that included the legendary city of Troy.
  • E. Lystra
    Lystra was an ancient city in the Roman province of Galatia, known from the New Testament as a place visited by the Apostle Paul and the hometown of his companion Timothy.
  • 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_69d8839174188190909f190097207065 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b0349bc88190938750f1e5af192a completed April 18, 2026, 4:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00cfc0dcd081909f715e0f2aad67c7 completed May 10, 2026, 6:34 p.m.
Created at: April 10, 2026, 5:21 a.m.