Triple
T9500125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naantali |
E229113
|
entity |
| Predicate | MoominWorldLocatedOn |
P18608
|
FINISHED |
| Object | Kailo Island |
—
|
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: Kailo Island | Statement: [Naantali, MoominWorldLocatedOn, Kailo Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MoominWorldLocatedOn Context triple: [Naantali, MoominWorldLocatedOn, Kailo Island]
-
A.
isLocatedOn
chosen
Indicates that one entity exists at or is situated upon the surface or area of another entity.
-
B.
livesOn
Indicates that one entity resides or has its home on or atop another entity (such as a surface, structure, or geographic feature).
-
C.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
D.
mythologicalLocation
Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
-
E.
depictsFictionalPlace
Indicates that one entity visually represents or portrays a place that exists only in fiction rather than in the real world.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983c308c8190bde6858ac1ca8ea5 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.