Triple
T31976482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samtgemeinde Flotwedel |
E816462
|
entity |
| Predicate | hasMemberVillage |
P47323
|
FINISHED |
| Object | Wienhausen |
—
|
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: Wienhausen | Statement: [Samtgemeinde Flotwedel, hasMemberVillage, Wienhausen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberVillage Context triple: [Samtgemeinde Flotwedel, hasMemberVillage, Wienhausen]
-
A.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
hasVillageCommunity
Indicates that an entity possesses, is associated with, or includes a village-level community as part of its structure or domain.
-
C.
hasVillageAccess
Indicates that an entity is permitted to enter, use, or benefit from the facilities, services, or areas of a particular village.
-
D.
isVillageDistrictOf
Indicates that one administrative unit is a village-level district that belongs to or is governed by a larger territorial entity.
-
E.
hasMemberMunicipality
chosen
Indicates that an administrative region or governing body includes a specific municipality as one of its constituent members.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 1, 2026, 12:11 a.m.