Triple
T23452055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedum |
E567806
|
entity |
| Predicate | locatedInMunicipalitySince |
P75195
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Bedum, locatedInMunicipalitySince, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMunicipalitySince Context triple: [Bedum, locatedInMunicipalitySince, 2019]
-
A.
partOfMunicipalitySince
chosen
Indicates that an entity has been included within and administratively belonging to a specific municipality starting from a given point in time.
-
B.
usedAsOfficialResidenceSince
Indicates that an entity has served as the formally designated official residence of another entity starting from a specified point in time.
-
C.
urbanStatusSince
Indicates the point in time since which an entity has held an urban status or classification.
-
D.
settledInYear
Indicates the specific calendar year in which an entity became established, inhabited, or formally settled in a particular place or status.
-
E.
locatedInPresentDayMunicipality
Indicates that an entity is situated within the boundaries of a specific municipality as it exists in the present day, regardless of historical administrative changes.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64ded5c8190bd50ac5b9bbb0f5f |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:52 p.m.