Triple
T18438670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ullsfjord |
E450463
|
entity |
| Predicate | administrativeRegionPreviously |
P65227
|
FINISHED |
| Object | Troms county |
—
|
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: Troms county | Statement: [Ullsfjord, administrativeRegionPreviously, Troms county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeRegionPreviously Context triple: [Ullsfjord, administrativeRegionPreviously, Troms county]
-
A.
laterAdministrativeRegion
chosen
Indicates that an entity became part of, or was replaced by, another administrative region at a later point in time.
-
B.
wasAdministrativeRegionFrom
Indicates that an entity served as an administrative region of another entity starting from a specified point in time.
-
C.
formerRegionBefore2016
Indicates that an entity was recognized as a region prior to the year 2016 but no longer holds that regional status after 2016.
-
D.
formerServesRegion
Indicates that an entity previously served, represented, or had official responsibility for a given region, but no longer does so.
-
E.
associatedAdministrativeRegion
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0ed6708190ae90efd8455ec352 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:29 a.m.