Triple
T3882266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akershus |
E92851
|
entity |
| Predicate | existedAsCountyUntil |
P52130
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Akershus, existedAsCountyUntil, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existedAsCountyUntil Context triple: [Akershus, existedAsCountyUntil, 2019]
-
A.
usedAsCountyNameUntil
Indicates that an entity served as the official name of a county up to a specified point in time.
-
B.
existedAsCountyOfDistrictOfColumbiaUntil
Indicates that an entity functioned as a county within the District of Columbia up to a specified end date or time.
-
C.
foundedAsCounty
Indicates that an administrative region or jurisdiction was originally established with the legal status and designation of a county.
-
D.
existedAsCountyOfDistrictOfColumbiaFrom
Indicates that an entity functioned as a county within the District of Columbia starting from a specified point in time.
-
E.
countySeatSince
Indicates that one place has served as the official county seat of a county starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:20 p.m.