Triple
T3326962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basin and Range National Monument |
E69937
|
entity |
| Predicate | permittedActivities |
P7913
|
FINISHED |
| Object | hiking |
—
|
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: hiking | Statement: [Basin and Range National Monument, permittedActivities, hiking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permittedActivities Context triple: [Basin and Range National Monument, permittedActivities, hiking]
-
A.
settingOfActivities
Indicates that a particular place or context serves as the environment in which certain activities occur or are carried out.
-
B.
awardedForActivitiesIn
Indicates that an award or recognition is given to an entity specifically because of activities carried out in a particular field, context, or domain.
-
C.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
D.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
E.
eligibleUses
chosen
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb16dc170819086a63e033e17d8b3 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.