Triple
T21542514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alteveer |
E531526
|
entity |
| Predicate | hasNeighbouringSettlements |
P63834
|
FINISHED |
| Object | other villages in De Wolden |
—
|
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: other villages in De Wolden | Statement: [Alteveer, hasNeighbouringSettlements, other villages in De Wolden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbouringSettlements Context triple: [Alteveer, hasNeighbouringSettlements, other villages in De Wolden]
-
A.
hasAdjacentSettlement
chosen
Indicates that one settlement is located directly next to or bordering another settlement.
-
B.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
C.
hasNearbyTown
Indicates that one location has a town situated close to it in geographic proximity.
-
D.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
E.
hasNearbyTownType
Indicates that one entity has, in its vicinity, a town of a specified type or classification.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb58c34808190b0eb54ba01e2cc13 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.