Triple
T28372483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Spider’s Web |
E718669
|
entity |
| Predicate | guidebookCoverage |
P27618
|
FINISHED |
| Object | Adirondack rock climbing guidebooks |
—
|
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: Adirondack rock climbing guidebooks | Statement: [The Spider’s Web, guidebookCoverage, Adirondack rock climbing guidebooks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidebookCoverage Context triple: [The Spider’s Web, guidebookCoverage, Adirondack rock climbing guidebooks]
-
A.
inGuidebook
Indicates that something is included or featured as an entry within a guidebook.
-
B.
hasGuidebook
Indicates that an entity possesses, is associated with, or is provided with a guidebook.
-
C.
guidebookArea
chosen
Indicates that one entity is a geographic or topical area covered or described within a guidebook.
-
D.
isGuidebookClassic
Indicates that something is recognized as a classic or authoritative guidebook within its domain or genre.
-
E.
coverLocation
Indicates that one entity serves as a covering or protective layer positioned at or over a specific location of another entity.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1 a.m.