Triple
T12287318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soum de Ramond |
E292862
|
entity |
| Predicate | hasMapLabel |
P13793
|
FINISHED |
| Object | Soum de Ramond |
E292862
|
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: Soum de Ramond | Statement: [Soum de Ramond, hasMapLabel, Soum de Ramond]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Soum de Ramond Context triple: [Soum de Ramond, hasMapLabel, Soum de Ramond]
-
A.
Soum de Ramond
chosen
Soum de Ramond is a prominent peak in the Pyrenees, known as one of the major summits of the Monte Perdido massif on the border between France and Spain.
-
B.
Lebrun
Lebrun is a French surname borne by various notable figures in politics, arts, and other fields.
-
C.
Le Bémont
Le Bémont is a small municipality in the Jura canton of Switzerland, situated on the Franches-Montagnes plateau and known for its rural, pastoral landscape.
-
D.
Surpierre
Surpierre is a small municipality in the canton of Fribourg in western Switzerland.
-
E.
Tournier
Tournier is a surname of French origin, sometimes used as a variant of the English surname Turner.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d1ffb208190a4b86d7d4ceee045 |
completed | April 10, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f634667db88190ac1368dc38daac73 |
completed | May 2, 2026, 5:29 p.m. |
Created at: April 8, 2026, 9:52 p.m.