Triple
T38702723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Peak |
E950182
|
entity |
| Predicate | positionInRidge |
P201958
|
FINISHED |
| Object | middle summit |
—
|
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: middle summit | Statement: [Second Peak, positionInRidge, middle summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRidge Context triple: [Second Peak, positionInRidge, middle summit]
-
A.
isOnRidgeWith
Indicates that two or more entities are located together along the same ridge or elevated crest.
-
B.
isOnRidgeBetween
Indicates that something is located on the ridge that lies between two other reference points or areas.
-
C.
hasRidgesTowards
Indicates that one entity has ridges that are oriented or directed toward another entity.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
associatedWithRidge
Indicates that one entity has a spatial, structural, or contextual connection or relationship to a ridge.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00383e868c819098fd17e25fcbdb04 |
completed | May 10, 2026, 7:48 a.m. |
| PD | Predicate disambiguation | batch_6a0037cc59688190b7b9da939a413db3 |
completed | May 10, 2026, 7:46 a.m. |
| PDg | Predicate description generation | batch_6a00383d83c08190af7bc00f17affd97 |
completed | May 10, 2026, 7:48 a.m. |
Created at: May 3, 2026, 4:33 p.m.