Triple
T4007912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ojców Castle |
E89571
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Ojców |
E91839
|
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: Ojców | Statement: [Ojców Castle, locatedIn, Ojców]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ojców Context triple: [Ojców Castle, locatedIn, Ojców]
-
A.
Ojców
chosen
Ojców is a small village in southern Poland known as a gateway to the picturesque Ojców National Park in the Kraków-Częstochowa Upland.
-
B.
Olsztynek
Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
-
C.
Opatów
Opatów is a historic town in south-central Poland known for its medieval architecture, including a Romanesque collegiate church and well-preserved town gate.
-
D.
Glogów
Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
-
E.
Oleśnica
Oleśnica is a historic town in southwestern Poland known for its Renaissance castle and well-preserved old town.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa647f80819081180eb267f1cfcc |
completed | March 9, 2026, 4:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c097a5c6a4819082f4b9bf113ea33b |
completed | March 23, 2026, 1:30 a.m. |
Created at: March 9, 2026, 3:34 p.m.