Triple
T26165182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther Peak |
E654228
|
entity |
| Predicate | includedInChallenge |
P169724
|
FINISHED |
| Object | Adirondack 46er challenge |
—
|
NE NERFINISHED |
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: Adirondack 46er challenge | Statement: [Panther Peak, includedInChallenge, Adirondack 46er challenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInChallenge Context triple: [Panther Peak, includedInChallenge, Adirondack 46er challenge]
-
A.
challengeIncludes
chosen
Indicates that a particular challenge contains, comprises, or is made up of the specified component, task, or element.
-
B.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
C.
hasBeenChallengedIn
Indicates that an entity has faced a challenge, contest, or dispute within a specified context, domain, or setting.
-
D.
usedToChallenge
Indicates that one entity was employed or relied upon by another as a means to confront, contest, or question something or someone.
-
E.
hadChallengeRound
Indicates that an entity participated in or was associated with a specific challenge round within a broader event or process.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 26, 2026, 8:32 p.m.