Triple
T8942843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lauttasaari |
E212944
|
entity |
| Predicate | urbanDistrictNumber |
P13282
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Lauttasaari, urbanDistrictNumber, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanDistrictNumber Context triple: [Lauttasaari, urbanDistrictNumber, 20]
-
A.
communityDistrictNumber
chosen
Indicates the specific community district identifier associated with an entity or location.
-
B.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
C.
cityDistrictLevel
Indicates that one administrative unit is a district-level subdivision within a given city in the territorial hierarchy.
-
D.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
E.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66d93978819084b1a5c7c5dd2372 |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.