Triple
T27558392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skjetten |
E695705
|
entity |
| Predicate | locatedInCountyBefore2020 |
P110432
|
FINISHED |
| Object | Akershus 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: Akershus county | Statement: [Skjetten, locatedInCountyBefore2020, Akershus county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountyBefore2020 Context triple: [Skjetten, locatedInCountyBefore2020, Akershus county]
-
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.
previousCounty
Indicates that one county was the immediately preceding county associated with an entity before the current or later county.
-
C.
establishedAsCountyInCurrentForm
Indicates that an administrative region became a county in its present organizational or territorial form on a specific date or during a specific period.
-
D.
countyAfter2020Reform
Indicates that an administrative county exists in its form or status as defined following the 2020 reform.
-
E.
unifiedAsCountyInYear
Indicates that multiple areas or jurisdictions were merged into a single county in the specified year.
- 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_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: April 27, 2026, 1:38 p.m.