Triple
T15077159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straume |
E380033
|
entity |
| Predicate | municipalityCentreSince |
P72646
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Straume, municipalityCentreSince, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalityCentreSince Context triple: [Straume, municipalityCentreSince, 2020]
-
A.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
districtHeadquartersSince
chosen
Indicates the time from which a particular location has served as the administrative headquarters of a specified district.
-
C.
partOfMunicipalitySince
Indicates that an entity has been included within and administratively belonging to a specific municipality starting from a given point in time.
-
D.
municipalityName
Indicates the official name assigned to a municipality.
-
E.
hasPopulationCentreFunction
Indicates that an entity serves as a population centre, fulfilling functions related to the concentration, residence, and support of a population.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fe5a208190823900b25e298dab |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:03 a.m.