Triple
T27799899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Palisade |
E702209
|
entity |
| Predicate | isAppealingTo |
P14484
|
FINISHED |
| Object | experienced mountaineers |
—
|
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: experienced mountaineers | Statement: [Middle Palisade, isAppealingTo, experienced mountaineers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAppealingTo Context triple: [Middle Palisade, isAppealingTo, experienced mountaineers]
-
A.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
B.
canBeAppealedTo
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
-
C.
alsoAppealsTo
chosen
Indicates that something attracts, interests, or is pleasing to an additional person, group, or audience beyond the primary one.
-
D.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
-
E.
ultimateAppealLiesTo
Indicates that the final level of appeal or review authority for a decision or case rests with a specified entity or body.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:33 p.m.