Triple
T29697168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taalintehdas |
E751382
|
entity |
| Predicate | isMainLocalCenterOf |
P41403
|
FINISHED |
| Object | Kemiönsaari |
—
|
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: Kemiönsaari | Statement: [Taalintehdas, isMainLocalCenterOf, Kemiönsaari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainLocalCenterOf Context triple: [Taalintehdas, isMainLocalCenterOf, Kemiönsaari]
-
A.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
B.
isCentreOf
Indicates that one entity serves as the central point, core, or focal location relative to another entity or context.
-
C.
isCentralLocalityOf
chosen
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
D.
centerIs
Indicates that one entity serves as the central point or middle position of another entity or space.
-
E.
isSelfCentralizingIn
Indicates that an entity is equal to its own centralizer within a larger structure, meaning all elements that commute with it are contained in it.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 7:21 p.m.