Triple
T33326928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michalovce |
E853289
|
entity |
| Predicate | hasNotableLakeNearby |
P17985
|
FINISHED |
| Object | Zemplínska šírava reservoir |
—
|
LITERAL 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: Zemplínska šírava reservoir | Statement: [Michalovce, hasNotableLakeNearby, Zemplínska šírava reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLakeNearby Context triple: [Michalovce, hasNotableLakeNearby, Zemplínska šírava reservoir]
-
A.
hasNearbyLake
chosen
Indicates that one entity is located close to or in the vicinity of a lake.
-
B.
hasNearbyLakeRegion
Indicates that one region is located close to a lake or lake-dominated area.
-
C.
hasLakeLandscape
Indicates that an entity features or is characterized by a landscape that includes a lake.
-
D.
hasLakes
Indicates that one entity possesses, contains, or is characterized by the presence of one or more lakes.
-
E.
hasNearbyArtificialLake
Indicates that one entity is located close to an artificial lake associated with or near another entity.
- F. None of above.
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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01b130f6808190b86442fb16930e6e |
completed | May 11, 2026, 10:36 a.m. |
| PD | Predicate disambiguation | batch_6a01b023157881909a802e06eced3e2f |
completed | May 11, 2026, 10:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.