Triple
T15091956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fagernes |
E360440
|
entity |
| Predicate | hasCountyCapitalRole |
P117280
|
FINISHED |
| Object | regional center in Innlandet |
—
|
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: regional center in Innlandet | Statement: [Fagernes, hasCountyCapitalRole, regional center in Innlandet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyCapitalRole Context triple: [Fagernes, hasCountyCapitalRole, regional center in Innlandet]
-
A.
hasCountySeatOf
Indicates that a place serves as the administrative county seat (capital) of a specified county.
-
B.
hasCountySeatWithRole
Indicates that a county has a designated county seat that fulfills a specific administrative or governmental role.
-
C.
hasCountySeatCity
Indicates that a county has a specific city that serves as its official administrative center or county seat.
-
D.
hasCountySeatRelation
Indicates that a specific place serves as the county seat (administrative center) of a particular county.
-
E.
hasCountySeatOn
Indicates that a county’s administrative center (county seat) is located on or adjacent to a specified geographic feature or infrastructure.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0027925788190b955fdc6626adf7d |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:04 a.m.