Triple
T28715502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Salt Mountain |
E729948
|
entity |
| Predicate | hasLiteralNameMeaning |
P64940
|
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, hasLiteralNameMeaning, Upper Salt Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiteralNameMeaning Context triple: [Upper Salt Mountain, hasLiteralNameMeaning, Upper Salt Mountain]
-
A.
hasLiteralMeaning
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
-
B.
hasLatinNameMeaning
Indicates that an entity’s Latin name conveys a specific meaning or refers to a particular concept.
-
C.
hasBaseNameMeaning
Indicates that an entity’s base name carries or is associated with a particular meaning.
-
D.
nameLiterallyMeans
chosen
Indicates that the literal meaning or direct translation of one entity’s name is given by the other entity.
-
E.
hasNameMeaningRelation
Indicates that there is a relationship between an entity and a name that conveys or encodes a particular meaning or significance.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 28, 2026, 5:50 a.m.