Triple
T27558567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fet |
E695709
|
entity |
| Predicate | hasNeighbouringMunicipalityFormer |
P33892
|
FINISHED |
| Object | Aurskog-Høland |
—
|
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: Aurskog-Høland | Statement: [Fet, hasNeighbouringMunicipalityFormer, Aurskog-Høland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbouringMunicipalityFormer Context triple: [Fet, hasNeighbouringMunicipalityFormer, Aurskog-Høland]
-
A.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
B.
neighbouringMunicipality
chosen
Indicates that one municipality directly borders and is adjacent to another municipality.
-
C.
wasMunicipalityIn
Indicates that an entity previously held the status of a municipality within a specified administrative or territorial unit.
-
D.
hasFormerMunicipalityOnWestSide
Indicates that an entity’s former municipality is located on its western side.
-
E.
hasFormerMunicipalityOnEastSide
Indicates that an entity previously functioned as a municipality located on the eastern side of another referenced entity.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 27, 2026, 1:38 p.m.