Triple
T33207448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Noyer (Savoie) |
E850051
|
entity |
| Predicate | locatedInMountainSubrange |
P204300
|
FINISHED |
| Object | Massif des Bauges |
E242427
|
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: Massif des Bauges | Statement: [Le Noyer (Savoie), locatedInMountainSubrange, Massif des Bauges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMountainSubrange Context triple: [Le Noyer (Savoie), locatedInMountainSubrange, Massif des Bauges]
-
A.
locatedInMountainRangeRegion
Indicates that a place or geographic entity is situated within the area covered by a specific mountain range.
-
B.
locatedInMountain
Indicates that something is situated within, on, or as part of a mountain.
-
C.
originatesFromMountainRange
Indicates that something has its source or beginning in a specific mountain range.
-
D.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
-
E.
associatedWithMountainRange
Indicates a relationship where something is connected or related in some way to a specific mountain range.
- F. None of above. chosen
Provenance (5 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a036fb4650c81908df9b9ec8ed8594b |
completed | May 12, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729bc6bfc8190a0a9b37a71c855cd |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a036f64dc648190a31cf944d3ea0f7d |
completed | May 12, 2026, 6:20 p.m. |
| PDg | Predicate description generation | batch_6a036fb36c348190b56c005402b05f6c |
completed | May 12, 2026, 6:21 p.m. |
Created at: May 1, 2026, 1:30 a.m.