Triple
T32728949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pansio-Perno district |
E836895
|
entity |
| Predicate | locatedInCountryCapitalOfRegion |
P5025
|
FINISHED |
| Object | Turku |
E90238
|
NE 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: Turku | Statement: [Pansio-Perno district, locatedInCountryCapitalOfRegion, Turku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountryCapitalOfRegion Context triple: [Pansio-Perno district, locatedInCountryCapitalOfRegion, Turku]
-
A.
capitalLocatedInRegion
Indicates that a capital city is geographically situated within a specific region.
-
B.
locatedInCountryCapitalOfProvince
Indicates that an entity is located in the country that contains the capital city of a specified province.
-
C.
locatedInCountryCapitalSystem
Indicates that an entity is situated in the capital city of a specified country within a country–capital relationship system.
-
D.
capitalLocationRegion
Indicates that a location serves as the capital city or administrative center of a specified region.
-
E.
locatedInCapital
chosen
Indicates that an entity is situated within the capital city of a specified region, country, or administrative area.
- F. None of above.
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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0311c202408190be88a85337aacf11 |
completed | May 12, 2026, 11:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36d5bddfa88190a275b935615cfce9 |
completed | June 20, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_6a0310b0c9c88190ab218d47d4f432ed |
completed | May 12, 2026, 11:36 a.m. |
Created at: May 1, 2026, 1:11 a.m.