Triple
T33754591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oppåkermoen |
E864939
|
entity |
| Predicate | isInFormerCounty |
P110432
|
FINISHED |
| Object | Akershus |
—
|
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: Akershus | Statement: [Oppåkermoen, isInFormerCounty, Akershus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInFormerCounty Context triple: [Oppåkermoen, isInFormerCounty, Akershus]
-
A.
hasFormerCounty
chosen
Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
-
B.
isInFormerRegion
Indicates that one entity is located within a geographic or administrative area that previously existed or had a different status or boundaries in the past.
-
C.
locatedInFormerState
Indicates that an entity is or was geographically situated within the boundaries of a political state that no longer exists in its former form.
-
D.
existedAsCountyUntil
Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
-
E.
formerlyInDistrict
Indicates that an entity was once located in or part of a particular district, but is no longer within that district.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96ea0c08190902a3d0e1f263e8c |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:45 a.m.