Triple
T6659839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Sanford |
E151445
|
entity |
| Predicate | hasProminentSouthFace |
P72149
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mount Sanford, hasProminentSouthFace, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentSouthFace Context triple: [Mount Sanford, hasProminentSouthFace, true]
-
A.
hasProminentAspect
Indicates that an entity possesses a particularly notable, dominant, or emphasized aspect or feature.
-
B.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
-
C.
hasPromontory
Indicates that one entity possesses or features a prominent raised area or projecting landform extending outward, typically into a lower area or body of water.
-
D.
locatedSouthWestOf
Indicates that one entity is positioned to the southwest of another entity, combining both a southern and western relative location.
-
E.
isEasternPeakOf
Indicates that one peak is the eastern member or counterpart within a set or pair of related peaks.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2:02 p.m.