Triple
T12957456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orłowo train station |
E310053
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Orłowo |
E78629
|
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: Orłowo | Statement: [Orłowo train station, locatedIn, Orłowo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orłowo Context triple: [Orłowo train station, locatedIn, Orłowo]
-
A.
Orłowo
chosen
Orłowo is a coastal district of Gdynia in northern Poland, known for its scenic cliffs, pier, and Baltic Sea beaches.
-
B.
Zułowo
Zułowo is a village in present-day Lithuania best known as the birthplace of Józef Piłsudski, a key figure in Poland’s struggle for independence.
-
C.
Ozorków
Ozorków is a town in central Poland, located in the Łódź Voivodeship and known historically for its textile industry and proximity to the city of Łódź.
-
D.
Grodkowo
Grodkowo is a settlement in northern Poland located within the Warmian-Masurian Voivodeship, a region known for its lakes and natural landscapes.
-
E.
Działdowo
Działdowo is a town in northern Poland known for its historical significance and location within the Warmian-Masurian Voivodeship.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e2c5bf481908ca6adcfd3354f71 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006ec7a4748190822e66a756bc95b9 |
completed | May 10, 2026, 11:40 a.m. |
Created at: April 9, 2026, 5:44 p.m.