Triple
T7071038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorce Mountains |
E164694
|
entity |
| Predicate | notablePeak |
P20909
|
FINISHED |
| Object | Turbacz |
E428995
|
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: Turbacz | Statement: [Gorce Mountains, notablePeak, Turbacz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Turbacz Context triple: [Gorce Mountains, notablePeak, Turbacz]
-
A.
Turbacz
chosen
Turbacz is the highest peak of Poland’s Gorce Mountains, known for its extensive forested slopes and panoramic views, and as a popular destination for hikers.
-
B.
Turek
Turek is a town in central Poland known historically for its textile industry and its location in the Greater Poland region.
-
C.
Kiszczak
Kiszczak is a Polish surname most notably associated with Czesław Kiszczak, a communist-era general and interior minister of Poland.
-
D.
Ciecere
Ciecere is a river in western Latvia that serves as one of the tributaries of the Venta River.
-
E.
Tachov
Tachov is a town in western Czechia that serves as an administrative center and local hub within the Plzeň Region.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4c862f481908d1faf6ed57774f1 |
completed | March 27, 2026, 8:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c79c8a1d788190b9ad25d6e6c460f7 |
completed | March 28, 2026, 9:16 a.m. |
Created at: March 27, 2026, 2:39 p.m.