Triple
T13649850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandåsen |
E326700
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Ombo |
E326700
|
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: Ombo | Statement: [Bandåsen, locatedOn, Ombo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ombo Context triple: [Bandåsen, locatedOn, Ombo]
-
A.
Ombo
chosen
Ombo is a large island in Rogaland county, Norway, known for its rural landscapes, agriculture, and coastal scenery.
-
B.
Birka
Birka was a major Viking Age trading center and early urban settlement located on the island of Björkö in present-day Sweden.
-
C.
Kenuzi-Dongola
Kenuzi-Dongola is a Nubian language of the Eastern Sudanic branch spoken primarily along the Nile in southern Egypt and northern Sudan.
-
D.
Kom Ombo
Kom Ombo is an Egyptian town on the Nile best known for its unique double temple dedicated to the gods Sobek and Horus.
-
E.
Mehen
Mehen is an ancient Egyptian protective serpent deity who coils around the sun god Ra to shield him from threats like the chaos serpent Apep.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc608466c81908f6d2c9c92cc86aa |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78afbf8948190ad38ea7529e52f16 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:52 p.m.