Triple
T13468335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wieprz River |
E311561
|
entity |
| Predicate | flowsNear |
P350
|
FINISHED |
| Object | Ryki |
E302294
|
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: Ryki | Statement: [Wieprz River, flowsNear, Ryki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ryki Context triple: [Wieprz River, flowsNear, Ryki]
-
A.
Ryki
chosen
Ryki is a small town in eastern Poland known for its location within the Lublin region and its local administrative and cultural role.
-
B.
Raki
Raki is a traditional Turkish anise-flavored alcoholic spirit, often enjoyed diluted with water alongside meze.
-
C.
Ryglice
Ryglice is a small town in southern Poland known for its rural character and location in the historical region of Lesser Poland.
-
D.
Rytro
Rytro is a village in southern Poland’s Lesser Poland Voivodeship, situated in the scenic Poprad Valley of the Western Carpathians and known as a local tourist and hiking destination.
-
E.
Rajokri
Rajokri is a village and rapidly urbanizing locality situated on the outskirts of Delhi, known for its proximity to the Delhi-Gurgaon border and the airport corridor.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf21e46081908a00c9acf54f270f |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f74629f1408190b54194fe794be39a |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 9, 2026, 9:42 p.m.