Triple
T35677910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imatra switchyard |
E1030914
|
entity |
| Predicate | gridCodeRegion |
P183612
|
FINISHED |
| Object | Nordic synchronous area |
—
|
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: Nordic synchronous area | Statement: [Imatra switchyard, gridCodeRegion, Nordic synchronous area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridCodeRegion Context triple: [Imatra switchyard, gridCodeRegion, Nordic synchronous area]
-
A.
gridCodeAuthority
Indicates that an authority or governing body is responsible for assigning, managing, or validating a specific grid code for an entity or location.
-
B.
subregionCodeFor
Indicates that one entity is the code assigned to identify a specific subregion of the other entity.
-
C.
countyRegion
Indicates that a county is located within, or is administratively part of, a larger geographic region.
-
D.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger state.
-
E.
governmentRegionFor
Indicates that a government entity has jurisdiction over or is associated with a specific geographic region.
- F. None of above. chosen
Provenance (4 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:05 p.m.