Triple
T28715483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Salt Mountain |
E729948
|
entity |
| Predicate | hasEnglishMeaningOfName |
P178037
|
FINISHED |
| Object | Upper Salt Mountain |
—
|
NE NERFINISHED |
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: Upper Salt Mountain | Statement: [Upper Salt Mountain, hasEnglishMeaningOfName, Upper Salt Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnglishMeaningOfName Context triple: [Upper Salt Mountain, hasEnglishMeaningOfName, Upper Salt Mountain]
-
A.
hasEnglishNameMeaning
Indicates that an entity is associated with an English-language name along with the meaning or semantic interpretation of that name.
-
B.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
C.
hasGivenNameMeaning
Indicates that a given name carries a particular meaning or semantic interpretation.
-
D.
hasMeaningInOriginLanguage
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
E.
isMeaningOfName
Indicates that one entity expresses or defines the meaning or interpretation of a given name.
- F. None of above. chosen
Provenance (4 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 28, 2026, 5:50 a.m.