Triple
T26122382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunteren |
E659005
|
entity |
| Predicate | hasNearbyHighestPointOfNetherlandsMainland |
P179455
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lunteren, hasNearbyHighestPointOfNetherlandsMainland, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHighestPointOfNetherlandsMainland Context triple: [Lunteren, hasNearbyHighestPointOfNetherlandsMainland, true]
-
A.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
B.
highestNearbyPeakElevationInFeet
Indicates the elevation in feet of the tallest peak located within a defined nearby area of a given reference point.
-
C.
nearestMainlandPoint
Indicates the relationship where a location is associated with the closest point on the mainland to that location.
-
D.
nearbyHunebed
Indicates that one entity is located close to a hunebed (a megalithic stone tomb), within a short spatial distance.
-
E.
nearestHigherPeak
Indicates that one peak is the closest peak that has a higher elevation than another specified peak.
- F. None of above. chosen
Provenance (4 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 26, 2026, 8:09 p.m.