Triple
T11955786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jyväskylän maalaiskunta |
E284548
|
entity |
| Predicate | sharesNameLanguage |
P15
|
FINISHED |
| Object | Finnish toponymy |
—
|
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: Finnish toponymy | Statement: [Jyväskylän maalaiskunta, sharesNameLanguage, Finnish toponymy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesNameLanguage Context triple: [Jyväskylän maalaiskunta, sharesNameLanguage, Finnish toponymy]
-
A.
sharesLanguageWith
Indicates that two entities use at least one common language for communication.
-
B.
languageOfWorkOrName
chosen
Indicates the language in which a work is created or a name is expressed.
-
C.
sharesNameRootWith
Indicates that two entities have names derived from the same linguistic root or base form.
-
D.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
E.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.