Triple
T5588653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heby Municipality |
E146820
|
entity |
| Predicate | ISO3166-1CountryCode |
P19525
|
FINISHED |
| Object | SE |
—
|
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 | Statement: [Heby Municipality, ISO3166-1CountryCode, SE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO3166-1CountryCode Context triple: [Heby Municipality, ISO3166-1CountryCode, SE]
-
A.
ISO3166-1Code
chosen
Indicates the standardized two- or three-letter country or territory code assigned under the ISO 3166-1 international standard.
-
B.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
C.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
-
D.
UNLOCODECountryCode
Indicates that an entity is associated with a specific country code as defined by the UN/LOCODE standard.
-
E.
ISO3166-2RegionCode
Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0209e892c8190b936a05ef2a14d36 |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.