Triple
T26406472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Thirst |
E663846
|
entity |
| Predicate | isDominantHighPointOf |
P39718
|
FINISHED |
| Object | San Clemente Island central-southern region |
—
|
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: San Clemente Island central-southern region | Statement: [Mount Thirst, isDominantHighPointOf, San Clemente Island central-southern region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDominantHighPointOf Context triple: [Mount Thirst, isDominantHighPointOf, San Clemente Island central-southern region]
-
A.
isMajorPeakOf
chosen
Indicates that one peak is a primary or most prominent summit within a specified mountain, range, or geographic area.
-
B.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
-
C.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
D.
dominatesSkylineOf
Indicates that one entity visually towers over and is the most prominent feature in the skyline of another location or area.
-
E.
highPointLocatedOn
Indicates that the highest point of one entity is situated on or atop another entity.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610f87374819084279ca5c2f3d32f |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:35 p.m.