Triple
T32833854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mänttä-Vilppula |
E839769
|
entity |
| Predicate | hasNeighboringFeatureType |
P140255
|
FINISHED |
| Object | lakes |
—
|
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: lakes | Statement: [Mänttä-Vilppula, hasNeighboringFeatureType, lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringFeatureType Context triple: [Mänttä-Vilppula, hasNeighboringFeatureType, lakes]
-
A.
hasNeighboringFeature
chosen
Indicates that one feature is located adjacent to or directly next to another feature in space.
-
B.
hasAdjacencyType
Indicates that one entity is related to another by a specific kind or category of adjacency (e.g., how they are positioned or connected next to each other).
-
C.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
D.
hasNeighbouringAdministrativeUnitType
Indicates that one administrative unit is directly adjacent to another administrative unit of a specified type.
-
E.
hasNeighboringObject
Indicates that one object is located adjacent to or directly next to another object in space.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 1, 2026, 1:16 a.m.