Triple
T16396112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katowice Airport |
E398185
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Pyrzowice |
—
|
NE NERFINISHED |
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: Pyrzowice | Statement: [Katowice Airport, locatedIn, Pyrzowice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyrzowice Context triple: [Katowice Airport, locatedIn, Pyrzowice]
-
A.
Pyrzowice
chosen
Pyrzowice is a village in southern Poland best known for hosting Katowice International Airport, one of the country’s major air transport hubs.
-
B.
Rakowice
Rakowice is a historic district in Kraków, Poland, known for its large military cemetery and proximity to the city center.
-
C.
Krapkowice
Krapkowice is a small town in southwestern Poland known for its location on the Oder River and its local industry, including paper and cement production.
-
D.
Pyskowice
Pyskowice is a small town in southern Poland, located in the Silesian Voivodeship and known for its historical architecture and regional industrial heritage.
-
E.
Szydłowiec
Szydłowiec is a historic town in central Poland known for its well-preserved Renaissance architecture and traditional sandstone quarrying.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cb3c708190b64341cb1410ed81 |
completed | April 18, 2026, 6:42 a.m. |
Created at: April 10, 2026, 5:09 a.m.