Triple
T3817880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayor of Helsinki |
E84299
|
entity |
| Predicate | capitalCityOffice |
P48856
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mayor of Helsinki, capitalCityOffice, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityOffice Context triple: [Mayor of Helsinki, capitalCityOffice, yes]
-
A.
capitalCityHeadquarters
Indicates that the headquarters of an organization or entity is located in the capital city of a specified region or country.
-
B.
seatOfGovernment
Indicates that a location serves as the administrative center where a government exercises its official authority and conducts its primary governing functions.
-
C.
capitalCityOfJurisdiction
Indicates that one entity is the primary city serving as the official capital of the specified jurisdiction or governing region.
-
D.
placeOfOffice
chosen
Indicates the location where an office or official position is held or based.
-
E.
capitalLocation
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.