Triple
T11407923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Briançonnais area |
E270286
|
entity |
| Predicate | hasSkiResort |
P1981
|
FINISHED |
| Object | Risoul |
E429937
|
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: Risoul | Statement: [Briançonnais area, hasSkiResort, Risoul]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Risoul Context triple: [Briançonnais area, hasSkiResort, Risoul]
-
A.
Risoul
chosen
Risoul is a French alpine ski resort and commune known for its extensive slopes and scenic location in the southern Alps.
-
B.
Shinrone
Shinrone is a small village in County Offaly, Ireland, known for its rural character and historic parish community.
-
C.
Shinkiari
Shinkiari is a town in Pakistan’s Khyber Pakhtunkhwa province, known for its agricultural surroundings and its location along the Karakoram Highway near Mansehra.
-
D.
Rinshi
Rinshi was a noblewoman of Japan’s Heian period and the principal wife of the powerful court regent Fujiwara no Michinaga.
-
E.
Hizaori
Hizaori is the former name of Asaka, a city located in Saitama Prefecture, Japan.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014e72748190a01bde2f0105cedb |
completed | April 9, 2026, 7:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e58d6eea4c81908319a590d2d9e177 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 8, 2026, 9:34 p.m.