Triple

T4432692
Position Surface form Disambiguated ID Type / Status
Subject Jan Lievens E95369 entity
Predicate workLocation P7 FINISHED
Object Antwerp E32042 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: Antwerp | Statement: [Jan Lievens, workLocation, Antwerp]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Antwerp
Context triple: [Jan Lievens, workLocation, Antwerp]
  • A. Antwerp chosen
    Antwerp is a major Belgian port city on the River Scheldt, renowned as a global center for the diamond trade and its historic Flemish art and architecture.
  • B. Ghent
    Ghent is a small unincorporated community and ski-area destination located in Raleigh County, West Virginia, United States.
  • C. Ghent
    Ghent is a historic city in the Flemish region of Belgium, known for its medieval architecture, canals, and role as a major cultural and economic center in the Middle Ages.
  • D. Leuven
    Leuven is a historic Belgian city known for hosting KU Leuven, one of Europe’s leading research universities, and for its vibrant academic and cultural life.
  • E. Vilvoorde
    Vilvoorde is a city in the Flemish Region of Belgium, located just north of Brussels and known as part of the capital’s broader metropolitan 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_69b3453c2a0c8190926b574c90766db9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3556cd83881908547aa311c4f17fa completed March 13, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69bfc1fe1188819097c3d382323571be completed March 22, 2026, 10:18 a.m.
Created at: March 12, 2026, 11:31 p.m.