Triple
T35382053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | west-central Poland |
E1022674
|
entity |
| Predicate | hasLakesRegion |
P127227
|
FINISHED |
| Object | Greater Poland Lakeland |
—
|
NE NERFINISHED |
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: Greater Poland Lakeland | Statement: [west-central Poland, hasLakesRegion, Greater Poland Lakeland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLakesRegion Context triple: [west-central Poland, hasLakesRegion, Greater Poland Lakeland]
-
A.
hasLakeRegion
chosen
Indicates that a place or geographic area includes or is associated with a specific lake region.
-
B.
hasLakes
Indicates that one entity possesses, contains, or is characterized by the presence of one or more lakes.
-
C.
hasFreshwaterLake
Indicates that one entity possesses, contains, or is associated with a freshwater lake.
-
D.
hasNearbyLakeRegion
Indicates that one region is located close to a lake or lake-dominated area.
-
E.
hasLakeThatRepresents
Indicates a relationship where a lake serves as a symbolic or representative feature for something, such as a place, concept, or 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.