Triple
T31195445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tałty Lake |
E795305
|
entity |
| Predicate | isPartOfPopularRegion |
P196502
|
FINISHED |
| Object | Masurian Lake District |
E220584
|
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: Masurian Lake District | Statement: [Tałty Lake, isPartOfPopularRegion, Masurian Lake District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfPopularRegion Context triple: [Tałty Lake, isPartOfPopularRegion, Masurian Lake District]
-
A.
isPopularTouristDestinationIn
Indicates that a place is widely visited and favored by tourists within a specified geographic area or region.
-
B.
regionPopularFor
Indicates that a particular region is well known or widely recognized for a specific activity, product, feature, or characteristic.
-
C.
connectsToTouristRegion
Indicates that one entity has a direct linkage or association to a tourist region, such as through location, access, or service provision.
-
D.
lessPopularInRegion
Indicates that one entity is less popular than another within a specified geographic region.
-
E.
isPopulousRegionOf
Indicates that a region has a large population and is located within or associated with a specified larger area or entity.
- F. None of above. chosen
Provenance (5 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e18937081908e6b1465f8348963 |
completed | June 11, 2026, 2:31 a.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: April 29, 2026, 9:09 p.m.