Triple
T22315818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stake Pass |
E551638
|
entity |
| Predicate | hasNavigationDifficulty |
P22896
|
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: [Stake Pass, hasNavigationDifficulty, moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationDifficulty Context triple: [Stake Pass, hasNavigationDifficulty, moderate]
-
A.
isDifficultToAccess
Indicates that reaching, using, or obtaining the referenced entity requires significant effort, obstacles, or special conditions.
-
B.
hasDifficultyWith
Indicates that one entity experiences problems, challenges, or lack of proficiency in dealing with, understanding, or performing something related to another entity.
-
C.
hasDifficultyContext
Indicates that something’s difficulty is defined, interpreted, or constrained within a particular situational or contextual framework.
-
D.
hasNavigationHazard
chosen
Indicates that something presents or contains a condition, object, or feature that poses a risk or obstacle to safe navigation.
-
E.
isDifficultToAccessBecauseOf
Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1575287688190aa642bb49b24f5a1 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.