Triple
T5849636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halland |
E129995
|
entity |
| Predicate | traditionalProvinceCode |
P21657
|
FINISHED |
| Object | SE-13 |
—
|
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: SE-13 | Statement: [Halland, traditionalProvinceCode, SE-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalProvinceCode Context triple: [Halland, traditionalProvinceCode, SE-13]
-
A.
traditionalProvince
Indicates that an entity is located in, associated with, or belongs to a historically recognized or customary provincial region rather than a modern administrative unit.
-
B.
hasPostalAbbreviationProvince
chosen
Indicates that a province is associated with a specific standardized postal abbreviation used in mailing addresses.
-
C.
postalRegionOf
Indicates that a given area or zone serves as the designated postal region for another location or address.
-
D.
hasProvinceName
Indicates that an entity (such as a province or region) bears or is associated with a specific province name.
-
E.
mainProvinces
Indicates that certain provinces are the primary or most significant administrative regions associated with a given entity.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.