Triple
T25536661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Kephart |
E640060
|
entity |
| Predicate | hasNearbyShelter |
P3789
|
FINISHED |
| Object | Icewater Spring Shelter |
—
|
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: Icewater Spring Shelter | Statement: [Mount Kephart, hasNearbyShelter, Icewater Spring Shelter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyShelter Context triple: [Mount Kephart, hasNearbyShelter, Icewater Spring Shelter]
-
A.
hasNearbySanctuary
Indicates that one entity has a sanctuary or place of refuge located close to it in space or distance.
-
B.
hasShelters
chosen
Indicates that one entity provides, contains, or is associated with one or more shelters for another entity or purpose.
-
C.
relativeShelterFrom
Indicates that one entity provides shelter or protection for another entity relative to some reference condition, location, or alternative.
-
D.
shelterType
Indicates the kind or category of shelter associated with an entity (e.g., tent, house, bunker).
-
E.
areaServedAsShelterFor
Indicates that one entity functioned as a shelter or refuge for another entity, providing protection or a safe place.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 3:23 p.m.