Triple
T29623740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | south side of Mount Baker |
E755071
|
entity |
| Predicate | hasTypicalCampArea |
P39717
|
FINISHED |
| Object | Railroad Grade moraine |
—
|
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: Railroad Grade moraine | Statement: [south side of Mount Baker, hasTypicalCampArea, Railroad Grade moraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalCampArea Context triple: [south side of Mount Baker, hasTypicalCampArea, Railroad Grade moraine]
-
A.
hasCampground
Indicates that one entity provides, contains, or is associated with a campground facility or area for another entity.
-
B.
typicalBaseCampArea
chosen
Indicates that a location is the usual or standard area used as a base camp for an activity, expedition, or operation.
-
C.
typicalCamp3Altitude_m
Indicates the usual elevation, in meters, at which the third camp in a sequence of camps is located.
-
D.
hasCampingSeason
Indicates that there is a defined period of the year during which camping is allowed, available, or typically occurs for the referenced entity.
-
E.
hasCampingStyle
Indicates that an entity is associated with a particular style or manner of camping.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 28, 2026, 6:36 p.m.