Triple
T13323432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohm |
E317372
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Amöneburg Basin |
E670173
|
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: Amöneburg Basin | Statement: [Ohm, region, Amöneburg Basin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amöneburg Basin Context triple: [Ohm, region, Amöneburg Basin]
-
A.
Bonaparte Basin
Bonaparte Basin is a large offshore sedimentary basin off northern Australia known for its significant oil and gas resources.
-
B.
Homburg Basin
chosen
Homburg Basin is a geological depression in the Taunus region of Hesse, Germany, known for encompassing the spa town of Bad Homburg vor der Höhe.
-
C.
Suhre basin
The Suhre basin is a river catchment area in Switzerland drained by the Suhre River, a tributary of the Aare, encompassing its surrounding landscape and hydrological system.
-
D.
Marsili Basin
Marsili Basin is a deep submarine basin in the southern Tyrrhenian Sea associated with active volcanic and tectonic processes.
-
E.
Ceresio basin
The Ceresio basin is the hydrological catchment area associated with Lake Lugano (also known as Ceresio) in the southern Alps between Switzerland and Italy.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9992c1fec8190bcb6a6bb3c973a24 |
completed | April 11, 2026, 12:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f2cd5688190a2a0db0f0295de83 |
completed | May 3, 2026, 10:10 a.m. |
Created at: April 9, 2026, 9:30 p.m.