Triple
T2791563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont Gerbier de Jonc |
E61939
|
entity |
| Predicate | approximateProminence |
P10298
|
FINISHED |
| Object | about 300 m |
—
|
LITERAL 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: about 300 m | Statement: [Mont Gerbier de Jonc, approximateProminence, about 300 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateProminence Context triple: [Mont Gerbier de Jonc, approximateProminence, about 300 m]
-
A.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
prominence
Indicates that an entity stands out in importance, visibility, or influence relative to others within a given context.
-
C.
areaPeakApprox
Indicates an approximate measurement or estimation of the peak area associated with an entity or event.
-
D.
topographicProminence
chosen
Indicates the height of a peak’s summit relative to the lowest contour line encircling it and no higher summit, expressing how much it stands out from surrounding terrain.
-
E.
hasMinimumProminence
Indicates that an entity meets or exceeds a specified threshold level of prominence or importance within a given context.
- F. None of above.
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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.