Triple
T21778475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Carrs |
E537642
|
entity |
| Predicate | summitConnectedTo |
P144832
|
FINISHED |
| Object | Swirl How via ridge |
—
|
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: Swirl How via ridge | Statement: [Great Carrs, summitConnectedTo, Swirl How via ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitConnectedTo Context triple: [Great Carrs, summitConnectedTo, Swirl How via ridge]
-
A.
hasSummitConnectionTo
chosen
Indicates a relationship where two entities are connected through a shared summit, peak, or highest point, such that one has a direct summit-related linkage to the other.
-
B.
summitUsedBy
Indicates that a particular summit is utilized or accessed by a specified entity (such as a person, group, or organization).
-
C.
summitAccessibleFrom
Indicates that a summit can be reached or accessed starting from a specified location or route.
-
D.
summitCount
Indicates the number of summits or peak ascents associated with an entity.
-
E.
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.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0462b094c81908207073c278a58fe |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.