Triple
T22624605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandvollan parish |
E558382
|
entity |
| Predicate | administersArea |
P34656
|
FINISHED |
| Object | Sandvollan area |
—
|
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: Sandvollan area | Statement: [Sandvollan parish, administersArea, Sandvollan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administersArea Context triple: [Sandvollan parish, administersArea, Sandvollan area]
-
A.
administersFrom
Indicates that an action, service, or process is carried out or managed starting from a particular source, location, or authority.
-
B.
regulatesArea
chosen
Indicates that one entity exercises control or governance over the spatial extent, scope, or domain of another entity.
-
C.
administrativeCouncilArea
Indicates that one entity is an administrative council area within which the other entity is located or governed.
-
D.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
E.
connectsAdministrativeArea
Indicates a relationship where one entity serves as a link or route between two administrative areas (such as regions, districts, or municipalities).
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3c5cb88190b172f9f92eb58d7f |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:01 p.m.