Triple
T21790593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Top |
E537958
|
entity |
| Predicate | summitCountContext |
P64502
|
FINISHED |
| Object | three closely spaced summits on Mount Le Conte |
—
|
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: three closely spaced summits on Mount Le Conte | Statement: [High Top, summitCountContext, three closely spaced summits on Mount Le Conte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitCountContext Context triple: [High Top, summitCountContext, three closely spaced summits on Mount Le Conte]
-
A.
summitCount
chosen
Indicates the number of summits or peak ascents associated with an entity.
-
B.
hasSummitCountApprox
Indicates that an entity is associated with an approximate number of summits or peak ascents.
-
C.
summitUsedBy
Indicates that a particular summit is utilized or accessed by a specified entity (such as a person, group, or organization).
-
D.
summitRepresents
Indicates that a summit serves as a formal venue or occasion in which certain positions, interests, or entities are presented, symbolized, or spoken for.
-
E.
summitView
Indicates a vantage point or perspective that is obtained from the top or highest point of something, such as a mountain or structure.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621f95cc8190a3e8619fbf29555a |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.