Triple
T32566707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Corcoran |
E832387
|
entity |
| Predicate | isProminentPeakOfState |
P124275
|
FINISHED |
| Object | California |
—
|
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: California | Statement: [Mount Corcoran, isProminentPeakOfState, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProminentPeakOfState Context triple: [Mount Corcoran, isProminentPeakOfState, California]
-
A.
isProminentPeak
Indicates that a peak stands out significantly in height, visibility, or importance compared to surrounding peaks.
-
B.
recognizedAsStateHighPointSince
Indicates that an entity has been officially acknowledged as the highest point of a state starting from a specified date or time.
-
C.
isEasternPeakOf
Indicates that one peak is the eastern member or counterpart within a set or pair of related peaks.
-
D.
isMostFamousPeakOf
Indicates that one peak is recognized as the most famous or well-known peak associated with a particular geographic area, range, or entity.
-
E.
isMostTopographicallyProminentIn
chosen
Indicates that an entity has the greatest topographic prominence within a specified area or group, exceeding that of all comparable entities.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c60e575c81908817e7817c85c550 |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.