Triple
T5200811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orminge |
E117387
|
entity |
| Predicate | hasFeature |
P182
|
FINISHED |
| Object | Orminge centrum |
E117387
|
NE 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: Orminge centrum | Statement: [Orminge, hasFeature, Orminge centrum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orminge centrum Context triple: [Orminge, hasFeature, Orminge centrum]
-
A.
Orminge
chosen
Orminge is a residential district and commercial center in the eastern Stockholm urban area, located within Nacka Municipality in Sweden.
-
B.
Ringsted
Ringsted is a historic market town and transport hub located in the central part of the Danish island of Zealand.
-
C.
Orting
Orting is a small city in western Washington State known for its scenic setting in the Puyallup River Valley with views of Mount Rainier.
-
D.
Horning
Horning is a picturesque village in Norfolk, England, known for its riverside setting within the Norfolk Broads.
-
E.
Sundbyvester
Sundbyvester is a district of Copenhagen located on Amager Island, known primarily as a residential urban area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a228e2c81908bfbd48ed9f2cd5e |
completed | March 20, 2026, 4:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bee0a6698c81908cc1fc7c15ffa5b7 |
completed | March 21, 2026, 6:17 p.m. |
Created at: March 20, 2026, 1:47 p.m.