Triple
T2207033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarpsborg |
E50822
|
entity |
| Predicate | hasCountyCapitalFunction |
P13896
|
FINISHED |
| Object | former Østfold county |
—
|
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: former Østfold county | Statement: [Sarpsborg, hasCountyCapitalFunction, former Østfold county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyCapitalFunction Context triple: [Sarpsborg, hasCountyCapitalFunction, former Østfold county]
-
A.
hasCountySeatFunction
chosen
Indicates that an entity serves as the official county seat, functioning as the administrative center for a county.
-
B.
hasCountySeatFeature
Indicates that a county has a specific feature serving as its official county seat (administrative center).
-
C.
hasCountySeatWithRole
Indicates that a county has a designated county seat that fulfills a specific administrative or governmental role.
-
D.
hasCountySeatOf
Indicates that a place serves as the administrative county seat (capital) of a specified county.
-
E.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1baa0948190b07ffc347a4f714e |
completed | March 7, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69abbda8a6dc8190aa855ce2d17194b1 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.