Triple
T19288195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Åsnes |
E482368
|
entity |
| Predicate | countyPreviously |
P110432
|
FINISHED |
| Object | Hedmark county |
—
|
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: Hedmark county | Statement: [Åsnes, countyPreviously, Hedmark county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countyPreviously Context triple: [Åsnes, countyPreviously, Hedmark county]
-
A.
previousCounty
Indicates that one county was the immediately preceding county associated with an entity before the current or later county.
-
B.
hasFormerCounty
chosen
Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
-
C.
formerDistrict
Indicates that one entity previously served as a district of another entity but no longer holds that status.
-
D.
cityPreviouslyLocatedIn
Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
-
E.
previousProvince
Indicates that one province was the immediately preceding administrative region of another in a temporal or historical sequence.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc043fa481909bbe281a70fb508e |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.