Triple
T10428375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gjerdrum |
E245843
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Romerike |
E421025
|
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: Romerike | Statement: [Gjerdrum, locatedOn, Romerike]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Romerike Context triple: [Gjerdrum, locatedOn, Romerike]
-
A.
Romerike
chosen
Romerike is a traditional district in southeastern Norway, northeast of Oslo, known for its mix of agricultural landscapes, growing suburbs, and key transport links including Oslo Airport Gardermoen.
-
B.
Horahane Roma
Horahane Roma are a subgroup of Roma people traditionally associated with Islam and found primarily in regions influenced by the former Ottoman Empire.
-
C.
Rommen
Rommen is a neighborhood in Oslo, Norway, situated within the Søndre Nordstrand borough.
-
D.
Trasmondo
Trasmondo is an Italian given name historically associated with the noble Conti di Segni family.
-
E.
Rajsko
Rajsko is a village in southern Poland located in the administrative district of Gmina Oświęcim in Lesser Poland Voivodeship.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea4a7dcc81909a830e08656a1c0c |
completed | April 7, 2026, 11:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87ea554888190bf2ef31e33c0ff14 |
completed | April 10, 2026, 4:37 a.m. |
Created at: April 6, 2026, 12:13 p.m.