Triple
T15197486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Älvsborg County |
E363173
|
entity |
| Predicate | wasEstablishedAsCounty |
P8950
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Älvsborg County, wasEstablishedAsCounty, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEstablishedAsCounty Context triple: [Älvsborg County, wasEstablishedAsCounty, 17th century]
-
A.
foundedAsCounty
chosen
Indicates that an administrative region or jurisdiction was originally established with the legal status and designation of a county.
-
B.
existedAsCountyUntil
Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
-
C.
hasFormerCounty
Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
-
D.
usedAsCountyNameUntil
Indicates that an entity served as the official name of a county up to a specified point in time.
-
E.
foundedAsCountySeat
Indicates that a place was originally established or designated to serve as the administrative center (county seat) of a county.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067fcc788190abdc083d4eadeb36 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.