Triple
T10848508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Dot Trail |
E256077
|
entity |
| Predicate | activityDifficulty |
P85385
|
FINISHED |
| Object | moderate |
—
|
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: moderate | Statement: [Red Dot Trail, activityDifficulty, moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityDifficulty Context triple: [Red Dot Trail, activityDifficulty, moderate]
-
A.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
B.
hasRecreationDifficulty
chosen
Indicates the level of challenge or effort required to engage in a particular recreational activity or experience.
-
C.
primaryLevelOfActivity
Indicates the main or most significant level at which an entity engages in a particular activity or operation.
-
D.
activityChallenged
Indicates that one entity has questioned, disputed, or formally contested the validity, appropriateness, or outcome of an activity involving another entity.
-
E.
difficultyRelativeTo
Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75114ca988190a0e730131adb2df0 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.