Triple
T12957312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orłowo Cliff |
E310049
|
entity |
| Predicate | hasView |
P854
|
FINISHED |
| Object | Orłowo Pier |
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 Pier | Statement: [Orłowo Cliff, hasView, Orłowo Pier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orłowo Pier Context triple: [Orłowo Cliff, hasView, Orłowo Pier]
-
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.
Orzysz
Orzysz is a small town in northeastern Poland known for its lakeside setting and proximity to extensive forests and military training grounds.
-
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.
Popielów
Popielów is a village in southwestern Poland that serves as the seat of the local administrative district (gmina) within Opole County.
-
E.
Wejherowo
Wejherowo is a historic town in northern Poland known for its baroque Calvary complex and role as a local cultural and administrative center.
- 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_69f6b8dc135c819091b7708d90db25cb |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 5:44 p.m.