Triple
T19778882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester of Finland |
E475079
|
entity |
| Predicate | appliedToCityRole |
P71023
|
FINISHED |
| Object | major industrial center of Finland |
—
|
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: major industrial center of Finland | Statement: [Manchester of Finland, appliedToCityRole, major industrial center of Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToCityRole Context triple: [Manchester of Finland, appliedToCityRole, major industrial center of Finland]
-
A.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
B.
focusCityRole
chosen
Indicates that a city serves a particular primary role or function within a broader geographic or organizational context.
-
C.
hasMajorCityRole
Indicates that an entity plays a significant official or functional role in the governance, administration, or key operations of a major city.
-
D.
endpointCityRole
Indicates the role or function that a city plays as an endpoint within a route, connection, or network.
-
E.
hasUrbanRole
Indicates that an entity plays a specific functional or social role within an urban or city context.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538230488190b45cd8aaec658f7f |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.