Triple
T15898440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orava Castle |
E385522
|
entity |
| Predicate | touristRegion |
P3030
|
FINISHED |
| Object | Orava |
E95035
|
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: Orava | Statement: [Orava Castle, touristRegion, Orava]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orava Context triple: [Orava Castle, touristRegion, Orava]
-
A.
Orava
chosen
Orava is a historical region in northern Slovakia and southern Poland, known for its mountainous landscapes, traditional villages, and the prominent Orava Castle.
-
B.
Orava River
The Orava River is a significant river in northern Slovakia that flows through the Orava region before joining the Váh River.
-
C.
Bystritsa River
The Bystritsa River is a significant watercourse in Russia that serves as one of the main tributaries feeding the Vyatka River system.
-
D.
West Morava
West Morava is a major river in central Serbia that serves as one of the two principal headwaters of the Velika Morava.
-
E.
White Váh
White Váh is one of the two main headwater streams that join to form the Váh River in northern Slovakia.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1563b0e4c8190b338672dfb122665 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000777c6a08190a4deed9952179be5 |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 4:51 a.m.