Triple

T6809741
Position Surface form Disambiguated ID Type / Status
Subject Opole University of Technology E156599 entity
Predicate locatedIn P40 FINISHED
Object Opole E28226 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: Opole | Statement: [Opole University of Technology, locatedIn, Opole]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Opole
Context triple: [Opole University of Technology, locatedIn, Opole]
  • A. Opole chosen
    Opole is a historic city in southwestern Poland, known as one of the country’s oldest urban centers and a regional cultural hub.
  • B. Opole Silesia
    Opole Silesia is a historical and cultural region in southwestern Poland, known for its mixed Polish-German heritage and centered around the city of Opole.
  • C. Opole Lubelskie
    Opole Lubelskie is a small town in eastern Poland known for its agricultural surroundings and location within the Lublin region.
  • D. Kalisz
    Kalisz is one of Poland’s oldest cities, located in the Greater Poland region and known for its historical architecture and cultural heritage.
  • E. Poznań
    Poznań is a historic and economically significant city in western Poland, known for its medieval Old Town, role as an early center of Polish statehood, and status as a major academic and industrial hub.
  • 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_69c68828b26c819090fe9df7612bbc27 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d30c741881909e220b05aa564bc2 completed March 27, 2026, 6:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69d181f4123c8190a15ee03b3156c6fd completed April 4, 2026, 9:26 p.m.
Created at: March 27, 2026, 2:16 p.m.