Triple
T33713572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borgarsyssel |
E863808
|
entity |
| Predicate | modernNameOfCenter |
P153035
|
FINISHED |
| Object | Sarpsborg |
—
|
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: Sarpsborg | Statement: [Borgarsyssel, modernNameOfCenter, Sarpsborg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernNameOfCenter Context triple: [Borgarsyssel, modernNameOfCenter, Sarpsborg]
-
A.
modernNameOfArea
Indicates that one area entity represents the current or modern name of another area entity.
-
B.
modernNameOfServedSettlement
Indicates that the object is the current, modern name of the settlement that is or was served by the subject (e.g., a facility, infrastructure, or service).
-
C.
historicalCenterFor
Indicates that one entity has served as a central or focal place of historical significance, activity, or development for another entity.
-
D.
formerMunicipalityCenterOf
Indicates that an entity once served as the administrative or central seat of a municipality that no longer exists in its former form.
-
E.
centerCityModernName
chosen
Indicates that the object is the current or modern name of the city that serves as the center or capital associated with the subject.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 1:44 a.m.